Mozilla Automation TeamJonathan AlmeidaSep 14, 20262 min readtutorialintermediate

Checkout a Github pull request from one-off contributions

Summary

Adds a git alias that fetches and checks out a branch from a contributor’s fork in one command, avoiding dependence on the GitHub `gh` CLI.

Define a git alias `co` that parses `<owner>:<branch>` arguments, fetches the branch via `git@github.com:<owner>/<repo>.git`, and checks out `FETCH_HEAD`.
Works with any Git host by adjusting the remote URL; not tied to the `gh` CLI.
Useful for one‑off PR reviews where you don’t want to add a permanent remote.

Provides a host‑agnostic, scriptable way to test external contributions without cluttering your repo with extra remotes, useful in automation or quick debugging scenarios.

5/10

devops cli automation git github

Related reading

Securing AI Pull Requests: Building a Deterministic AST Audit Harness in GitHub Actions sitepoint.com
A step‑by‑step tutorial for building a deterministic AST‑based security scanner that runs in GitHub Actions to catch prototype‑pollution, high‑entropy secrets, and unauthorized network egress in AI‑generated pull requests.
SitePointsitepoint.com3d19 min
Building Multi-Tier CI/CD Verification Gates for AI Pull Requests sitepoint.com
AI-generated code often passes basic CI but contains subtle bugs like vacuous tests or off-by-one errors. This article details a multi-tier CI/CD pipeline using AST analysis, property-based testing, and mutation testing to catch these issues and annotate GitHub PRs with actionable SARIF reports.
SitePointsitepoint.com2d17 min
One command per issue: git worktree, tmux and Claude Code bjornjohansen.com
The post introduces `claude-work`, a Bash helper that creates a git worktree, starts a tmux session, and launches Claude Code for a given issue, keeping each AI‑driven task isolated. It also handles safe re‑attachment and cautious cleanup to avoid losing work.
Bjørn Johansenbjornjohansen.com1mo4 min
Reinventing issue tracking: Local-first and Git-native manganin.dev
A devlog describing how Manganin’s issue tracker stores issues in a dedicated Git repo as plain files, after rejecting earlier approaches that tried to embed issue data in the code tree or Git refs. The author explains the pitfalls of using refs for issue storage, shows the low‑level Git commands needed for that approach, and then outlines the final design: a hidden sister repository where each i…
Lobstersmanganin.dev6d6 minHN1 lobste.rs27
Replacing Pull Requests with Delta zed.dev
Lobsterszed.dev6dHN144101 lobste.rs16
Three AI models review every merge request. Then they argue.bjornjohansen.com
A GitLab CI gate runs three isolated LLMs (Claude, GPT, Grok) on every merge request, forces them to exchange findings with code‑backed evidence, and decides mergeability via a deterministic voting function that only blocks on findings with independent confirmation.
Bjørn Johansenbjornjohansen.com25d6 min

Checkout a Github pull request from one-off contributions

Summary

Related reading

Securing AI Pull Requests: Building a Deterministic AST Audit Harness in GitHub Actionssitepoint.com

Building Multi-Tier CI/CD Verification Gates for AI Pull Requestssitepoint.com

One command per issue: git worktree, tmux and Claude Codebjornjohansen.com

Reinventing issue tracking: Local-first and Git-nativemanganin.dev

Replacing Pull Requests with Deltazed.dev

Three AI models review every merge request. Then they argue.bjornjohansen.com

Securing AI Pull Requests: Building a Deterministic AST Audit Harness in GitHub Actions sitepoint.com

Building Multi-Tier CI/CD Verification Gates for AI Pull Requests sitepoint.com

One command per issue: git worktree, tmux and Claude Code bjornjohansen.com

Reinventing issue tracking: Local-first and Git-native manganin.dev

Replacing Pull Requests with Delta zed.dev