build: add stale issue action #4072
Conversation
| 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. |
There was a problem hiding this comment.
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).
| 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 | ||
| days-before-close: 30 | ||
| stale-issue-label: stale |
There was a problem hiding this comment.
existing label stalled can probably be removed if this PR is merged
stalled
|
cc @nodejs/actions |
|
/cc @Trott |
PR-URL: #4072 Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com> Reviewed-By: Rich Trott <rtrott@gmail.com>
|
landed in 5b6b462 |
closes nodejs/admin#757
Draws off of nodejs/node#42085 to implement very generous stale issue management to the help repo.
As an initial draft I am targeting a 3 year staleness mark - which would mark these issues
Since this is the first time a workflow action is in this repo - I am unsure if anything else needs to be configured on the admin side.