Stale label remains after pushing a new commit
@v-chiranjib-swain is already working on this.
Since Oct 29, 2026.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 70/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github-actions, typescript
- Domain
- ci-cd
Research direction
Start by tracing how the action checks a pull request’s updated_at timestamp and applies the remove-stale-when-updated setting; the issue does not name specific files or tests. Reproduce with the listed steps using a normal push, then run the relevant action tests. Done means the stale label is removed on the next run after a new commit updates the PR.
Written by the indexing model from the issue text.
Description
Description:
Pushing a new commit to a stale PR updates its GitHub updated_at timestamp, but the next action run leaves the stale label in place. This conflicts with the documented behaviour of remove-stale-when-updated.
Action version:
11.0.0
Platform:
- Ubuntu
- macOS
- Windows
Runner type:
- Hosted
- Self-hosted
Repro steps:
- Enable
remove-stale-when-updated: true(the default). - Let the action mark an open PR as stale.
- Wait at least a minute, then push a new commit to the PR branch using a normal, non-force push.
- Make no other changes: no comments, reviews, or label changes.
- Run the action again and ensure it processes the PR.
Expected behavior:
The stale label is removed because the push updated the PR’s updated_at timestamp.
Actual behavior:
The stale label remains.
- Dominant language
- TypeScript
- Stars
- 1.7k
- Forks
- 438
- Avg merge
- 27d 8h
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from actions/stale
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 52/100
-
Closing items while paginating can skip open pull requestsPossibly taken @v-chiranjib-swain claimed this 93 days ago. Openbug
-
Ignore issues which has linked open PRsPossibly taken A pull request linked to this issue is open or already merged. Openfeature request
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
feature request
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
feature request
Difficulty 3/5 1-2 days Newbie friendliness 48/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
feature request needs triage
Difficulty 1/5 1-3 hours Newbie friendliness 69/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/symphony#91 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
solidjs/solid-docs#1716 ·
Maintainers usually reply within 1 day