Feature / Question: option to force negate `exempt-issue-labels` when having specific label (override)

Open
#860 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

The issue does not name any files, tests, or entry points. Start by locating where exempt-issue-labels is parsed and applied during stale issue eligibility checks; define the override behavior and verify it with a focused test covering an exempt label combined with the proposed force-inclusion label.

Written by the indexing model from the issue text.

Description

enhancement

The problem

Currently when defining exempt-issue-labels, for example bug, the issue will always be excluded, even if the issue has some kind of label like needs more information applied.

The solution

A option to have a force-overwrite for specific labels to always be included


Example:
when having a issue with label bug, which is a label in exempt-issue-labels, it will always be excluded, even if it requires more information and has a label like needs more information (meaning awaiting user response) and should then be included in the stale workflow.


I could not find a way to do this, so this is a question or a feature-request.

Dominant language
TypeScript
Stars
1.7k
Forks
438
Avg merge
27d 8h
Merged PRs (30d)
1

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/stale

All issues in actions/stale

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.