build: add stale issue action #4072
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,36 @@ | ||
| name: Close stale issues | ||
| on: | ||
| workflow_dispatch: | ||
| schedule: | ||
| # Run every day at 1:00 AM UTC. | ||
| - cron: 0 1 * * * | ||
|
|
||
| # yamllint disable rule:empty-lines | ||
| env: | ||
| CLOSE_MESSAGE: > | ||
| There has been no activity on this issue | ||
| and it is being closed. If you feel closing this issue is not the | ||
| right thing to do, please leave a comment. | ||
| WARN_MESSAGE: > | ||
| There has been no activity on this issue for | ||
| 3 years and it may no longer be relevant. | ||
| It will be closed 1 month after the last non-automated comment. | ||
| # yamllint enable | ||
|
|
||
| jobs: | ||
| stale: | ||
| if: github.repository == 'nodejs/help' | ||
| runs-on: ubuntu-latest | ||
| steps: | ||
| - uses: actions/stale@v4 | ||
| with: | ||
| repo-token: ${{ secrets.GITHUB_TOKEN }} | ||
|
There was a problem hiding this comment. are these tokens available at the org level? |
||
| # 3 years. this number is chosen to target around 25 initial issues, with then a natural flow as time progresses | ||
| days-before-stale: 1095 | ||
AugustinMauroy marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| days-before-close: 30 | ||
| stale-issue-label: stale | ||
|
There was a problem hiding this comment. existing label |
||
| close-issue-message: ${{ env.CLOSE_MESSAGE }} | ||
| stale-issue-message: ${{ env.WARN_MESSAGE }} | ||
| # max requests it will send per run to the GitHub API before it deliberately exits to avoid hitting API rate limits | ||
| operations-per-run: 30 | ||
| remove-stale-when-updated: true | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought about adding info about where better places to post help might be, but per conversation within nodejs/admin#757 I think we can proactively put that on the front-end of issue creation (template, README, https://github.com/marketplace/actions/welcome-new-users)
these messages over in nodejs/node#42085 also included a link to docs on how feature requests are managed. If we need to document this policy somewhere, I am happy to add that too (I just don't know where, or if it's even needed).