rajbos / rajbos/github-fork-updater
When the update fails, the issue is still closed
Open
Nobody has claimed this yet.
bug
- Dominant language
- PowerShell
- Stars
- 19
- Forks
- 36
- PR merge metrics
- No merged PRs in 30d
Description
When the update fails (for example because the used Access Token does not have enough rights, we do not pick up that failure and still close the issue. We should tell the user the error happened and leave the issue open.
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 files, tests, or entry points are named. Trace the update flow and its failure handling first, then verify that an update error is reported to the user and the issue remains open instead of being closed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100