wolfi-dev / wolfi-dev/wolfictl
wolfictl update: intermittent `failed to propose changes” errors
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 73
- Forks
- 86
- Avg merge
- 7d 7h
- Merged PRs (30d)
- 15
Description
On wolfi-os we are seeing intermittent errors with auto issues being created
example https://github.com/wolfi-dev/os/issues/1639
I've been running the bot on my fork and not been able to recreate. My current best guess is the git repo that branches and PRs are created from is getting into a bad state somehow.
Need to investigate, adding more logging could help
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
No file or test is named. Start by tracing the wolfictl update flow that creates auto issues, compare it with wolfi-dev/os#1639, and inspect repository state around branch and pull request creation while adding logging where needed. Done means identifying and fixing the cause of the intermittent “failed to propose changes” error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github, go
- Domain
- cli, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100