LouisBrunner / LouisBrunner/checks-action
Required status check not fulfilled randomly using this action to set the required check
- Dominant language
- TypeScript
- Stars
- 277
- Forks
- 64
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 3
Description
We are using this action to set to `neutral` a check that is marked as required in the branch protections, when there is no code change in the project.
From time to time this setting fails (but the action completes correctly, without error), and the PRs gets stuck, waiting for that required status check to be fulfilled. Sometimes retrying is enough for the process to work properly.
Would it be possible to add a retry to validate that the check has been set correctly? Maybe as an input parameter, configurable by the user. This could be useful also for cases where the Github API returns an unexpected error, or some rate-limit has been reached.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue does not name files or tests. Start by tracing the action's GitHub Checks API call that sets the required check to neutral and inspect how action inputs are defined. Done means a configurable retry can verify or repeat the check update, including transient API or rate-limit failures, with tests covering the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100