rajbos / rajbos/github-fork-updater
Check if the changes are present already in the fork
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 19
- Forks
- 36
- PR merge metrics
- No merged PRs in 30d
Description
I have seen issues where the fork had added commits, then send in a PR to the parent. After the PR has been accepted, the github-fork-updater still finds upstream changes (as does the GitHub UI btw), and then generates an update issue. The delta view will show no updates, since the commit is already in the fork....
No sure how to check this and prevent the issue from being created.
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
No file or test is named; start by tracing the fork/upstream comparison that produces the update issue and reproduce the case where the commit already exists in the fork. Done means the updater recognizes that state and does not create an issue when the delta view has no updates.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, powershell
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100