Allow labeling with no changed files

Open
#932 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
58/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
github-actions, typescript
Domain
ci-cd, devops

Research direction

No file or test is named in the issue. Locate the action's handling of pull requests with zero changed files and its branch-name labeling configuration, then update the relevant tests so the default still skips these PRs while the opt-in behavior labels them from branch rules only.

Written by the indexing model from the issue text.

Description

feature request

Description:

I would like the option to still label if the number of changed files is 0, based on the branch name.

Justification:

Some PRs have no file changes and simply exist to update commit history, even though the effective diff is 0. This is somewhat common in some release branching strategies. It would be nice if these PRs could still be labeled, even though they have no changes. Only the branch name labeling rules would apply in this scenario.

I think the default behavior of skipping labeling with no changes is reasonable, but providing an option via the action config to NOT skip labeling with no changes would be useful in the scenario described above.

Are you willing to submit a PR?

Yes!

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.