Add logging to show why a label gets assigned or not.
Open
Nobody has claimed this yet.
enhancement
needs eyes
- Dominant language
- TypeScript
- Stars
- 2.5k
- Forks
- 492
- PR merge metrics
- No merged PRs in 30d
Description
It would be handy if the action logged statements when a given path in PR match or doesn't rules in the file .github/labeler.yml.
For example, the action got kicked out, but no label was assigned, and based on this 👇 it's hard to understand why.
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 tracing how the action reads .github/labeler.yml and evaluates a changed path against its rules, then inspect any existing action logging. Done means the action logs enough detail to explain both matching and non-matching paths when labels are or are not assigned.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100