Remove the stale label when a PR is closed or merged

Open
#1,303 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reading the actions/stale workflow and how it currently applies the stale label. Trace the proposed remove-pr-stale-when-closed and remove-pr-stale-when-merged options, then verify both manual and automatic PR closure or merge cases no longer leave the label behind.

Written by the indexing model from the issue text.

Description

feature request

Description:
Remove the stale label when a PR is closed or merged

It would be helpful if actions/stale could automatically remove the stale label once a pull request is either merged or closed. A PR that has been merged or intentionally closed is no longer stale, so keeping the label is misleading.

Proposed configuration options could include something like:
remove-pr-stale-when-closed
remove-pr-stale-when-merged

This should ideally cover both cases:

  • PRs closed or merged manually by users.
  • PRs closed automatically by actions/stale workflow.

Currently, the stale label remains even after closure, and the action provides no way to clean it up without an additional workflow. Adding this feature would help keep repositories cleaner and labels more meaningful.

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.