brandonchinn178 / brandonchinn178/hooky
Be more resilient to concurrent git operations
Open
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 29
- Forks
- 2
- Avg merge
- 4h 37m
- Merged PRs (30d)
- 4
Description
If git operations are being run concurrently (e.g. by the IDE), various hooky actions might error with lock issues. Hooky should retry any issues with git locks
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
Start by locating the code that runs git operations for hooky actions and review how lock errors are currently surfaced. Reproduce concurrent git activity if possible, then add retry behavior for git lock failures and verify that other errors are not hidden.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, haskell
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100