transparency-dev / transparency-dev/tesseract
Automatically create an issue when the ci workflow fails X times in a row
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 37
- Forks
- 18
- Avg merge
- 19h 22m
- Merged PRs (30d)
- 15
Description
This will make sure humans can look into failures.
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 CI workflow referenced in the issue and determine how consecutive failures could be counted across runs. Clarify the value of X, the issue-creation mechanism, and the expected behavior before implementing; done means an issue is created only after the specified number of consecutive failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100