coverallsapp / coverallsapp/github-action
Feature Request: option to avoid failing on 5XX response
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 520
- Forks
- 78
- PR merge metrics
- No merged PRs in 30d
Description
As a user, I would like to be able to ignore server errors which are transient or outside of my control (e.g. 5XX HTTP response codes, such as the Gateway Timeout (504) errors I received last night) while not ignoring errors which are permanent or may be fixable on my end (e.g. due to missing token, account suspension, etc. - presumably 3XX or 4XX response codes?).
My understanding is that fail-on-error: false will cause the action to succeed after any server error, which could cause fixable errors to be overlooked, and that there is no option or combination of options which would achieve the desired behavior. Is that correct?
Is that a feature you would consider adding? Perhaps by updating fail-on-error to take another value indicating failure should occur for errors which may be fixable by the user (e.g. user, permanent, etc.)?
Thanks for considering,
Kevin
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 action's handling of the fail-on-error option and where HTTP response codes are classified. Check how 5XX, 3XX, and 4XX responses currently affect the action result, then define the requested behavior and verify that transient server errors can be ignored without hiding user-fixable errors.
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
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100