Dangling Commits cause bad PR checkouts
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 8.9k
- Forks
- 2.8k
- PR merge metrics
- No merged PRs in 30d
Description
Related to #299 and #237, we've found that a dangling/unreachable commit following a force push is now being used as the merge commit on every PR in the repository. We've tested several prior versions of actions/checkout and have reproduced the result. This run occurs in a private repository, so I can't share the log and commit info unfortunately.
Contributor guide
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
The issue names no files, tests, logs, or entry points. Start by reproducing a pull request checkout after a force push with a dangling commit, then verify that the dangling commit is no longer selected as the merge commit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100