Make not finding the PR an error
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.5k
- Forks
- 492
- PR merge metrics
- No merged PRs in 30d
Description
Description:
I would like an input so I can decide that this error 👇 should be an error and not a warning.
Justification:
It is easy to break things such that PRs can't be found (e.g. moving to least-permissions and accidentally removing read access). When this happens, there is no feedback that labeler has stopped working; you can only find this warning if you go look for it.
We have additional automation that runs based on labels, When labeler fails, that automation does the wrong thing. For example, we require 2 approvals on PRs with the Migration label, which is added by labeler based on files changed. When it fails, the PR doesn't get the label, and we allow it to merge with only 1 approval.
Are you willing to submit a PR?
Sure.
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 path that emits the warning when a pull request cannot be found and the action-input definitions for labeler. Add coverage for the requested opt-in error behavior and verify that the existing warning behavior remains unchanged when the input is not enabled.
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
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100