Ability to ignore label changes as "updates"
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- github-actions, typescript
Research direction
Start by tracing how actions/stale v9 determines whether a pull request has been updated and how label operations affect that decision. The example workflow shows the cascading stale-label case; done means providing a documented way to ignore label changes while preserving normal update handling. No source file or test is named in the issue.
Written by the indexing model from the issue text.
Description
Description:
A way to ignore labeling as an "update". When the action adds a stale label to a PR, that PR is now considered "updated" as of that time, and is no longer stale during the next run.
Justification:
Trying to have cascading stale levels, however, when a stale label is added the PR is now considered "updated" and no longer stale on the next run, removing that stale level on the next run.
Are you willing to submit a PR?
Unsure, I wouldn't know where to start here.
Example workflow:
name: Stale PR Management
permissions:
issues: write
pull-requests: write
on:
pull_request:
types: [opened]
schedule:
- cron: '0 * * * *' # Runs every hour
workflow_dispatch:
jobs:
label-new-prs:
runs-on: ubuntu-latest
if: github.event_name == 'pull_request' && github.event.action == 'opened'
steps:
- uses: actions/github-script@v8
with:
script: |
await github.rest.issues.addLabels({
owner: context.repo.owner,
repo: context.repo.repo,
issue_number: context.issue.number,
labels: ['🌱 fresh']
});
mark-relic:
runs-on: ubuntu-latest
if: github.event_name == 'schedule' || github.event_name == 'workflow_dispatch'
steps:
- uses: actions/stale@v9
with:
repo-token: ${{ secrets.GITHUB_TOKEN }}
days-before-stale: 15
days-before-close: -1
days-before-issue-stale: -1
stale-pr-label: '🗿 relic'
labels-to-remove-when-unstale: '🗿 relic'
labels-to-remove-when-stale: '🌱 fresh,🍞 stale'
exempt-pr-labels: ''
operations-per-run: 100
mark-stale:
runs-on: ubuntu-latest
if: github.event_name == 'schedule' || github.event_name == 'workflow_dispatch'
needs: mark-relic
steps:
- uses: actions/stale@v9
with:
repo-token: ${{ secrets.GITHUB_TOKEN }}
days-before-stale: 7
days-before-close: -1
days-before-issue-stale: -1
stale-pr-label: '🍞 stale'
labels-to-add-when-unstale: '🌱 fresh'
labels-to-remove-when-unstale: '🗿 relic,🍞 stale'
labels-to-remove-when-stale: '🌱 fresh'
exempt-pr-labels: '🗿 relic'
operations-per-run: 100
- 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
-
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
-
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
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
solidjs/solid-docs#1716 ·
Maintainers usually reply within 1 day
-
bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Progress indicated by console logs is off by onePossibly taken @marceliwac claimed this today. Openbug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
aws-samples/aws-cdk-examples#1336 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
melgarafael/DeskcommCRM#4999 · 1 comment ·
Maintainers usually reply within 1 day
-
type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days