oxidecomputer / oxidecomputer/buildomat
Worth documenting that PR jobs always run on the branch tip, not on the speculative merge
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 72
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
By default, GitHub Actions CI runs PR jobs on a speculative merge commit between the tip of the PR branch and the target branch as of the time the PR was last updated. But buildomat runs CI against the PR tip.
On the GHA side, this is hinted at in https://github.com/actions/checkout/?tab=readme-ov-file#checkout-pull-request-head-commit-instead-of-merge-commit but is not as clear as it could be.
I think it's worth documenting this clearly because it's a fairly common source of confusion.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the issue description and the linked GitHub Actions checkout documentation. Identify where buildomat's documentation explains pull-request job revisions, then document that buildomat runs against the PR branch tip rather than a speculative merge commit. Done means the distinction and its source of confusion are clear to users.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100