Add ability to exclude some types of updates from calculation of last update time

Open
#1,243 4 comments 5 reactions 0 assignees View on GitHub

@neenhouse is already working on this.

Since Aug 4, 2026.

  • #1358 by @neenhouse — open

Assessment

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

Research direction

Start by reading the action's existing configuration and tracing how it calculates the last update time. Define how users select update types to ignore and which bot users' comments are excluded, then add coverage for label changes and comments from ignored users so the configured behavior is verified.

Written by the indexing model from the issue text.

Description

feature request

Description:
Configure the types of updates that impact the last updated time.

Justification:
Justification or a use case for your proposal.

My project uses automation of various labels on PRs. If these automated labels are changed, I would like those changes ignored from this action's perspective. One example is a needs-rebase label that gets added if a PR goes into conflict with main. I've noticed that issues are staying open longer as a result.

Related: when a bot adds the needs-rebase label, it also adds a comment. It would be helpful to be able to ignore comments from a set of users (bots) for my use case, as well.

Thanks for the consideration!

Dominant language
TypeScript
Stars
1.7k
Forks
438
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/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.