Adding label and logging when paths aren't matched

Open
#664 3 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
github-actions, typescript
Domain
ci-cd, devtools

Research direction

Start by reviewing the existing path-matching flow and the V5 changes; the issue does not name specific files or tests. Determine how unmatched paths can be surfaced for every pull request, then verify that labels and logging expose the missed paths without disrupting existing labeling. Confirm whether commenting is part of the accepted behavior.

Written by the indexing model from the issue text.

Description

feature request

Description:

Handle paths that weren't matched by adding a label and logging (and commenting?) the list of missed paths, so the labeler file can be easily updated.

Justification:
I need all my paths to be labeled or ignored and with ongoing development it will be hard to maintain unless we have systems in place raising visibility of missing paths. #79 doesn't solve this, ideally this would happen for all PRs regardless of the file status.

Are you willing to submit a PR?
Yes, but, TS isn't my tool of trade and when I looked into v4.0.3, it seemed to require inverting the whole process, figured someone who knew the codebase better could come up with a less invasive solution. I've yet to look again since then and I'm not sure if it would be easier with the V5 changes.

Dominant language
TypeScript
Stars
2.5k
Forks
488
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from actions/labeler

All issues in actions/labeler

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.