Add ability to exclude some types of updates from calculation of last update time
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
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
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
- 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
-
Stale label remains after pushing a new commitPossibly taken @v-chiranjib-swain claimed this 21 days ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 52/100
-
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
-
awaiting-final-review request-icon
Difficulty 1/5 Under an hour Newbie friendliness 70/100
homebridge/plugins#1376 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
mindfold-ai/Trellis#672 ·
-
p1 state:active track
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
StellarCanary/ProtocolCanary-Action#698 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
pear-devs/pear-desktop#4839 ·
Maintainers usually reply within 1 day