-
Notifications
You must be signed in to change notification settings - Fork 5.3k
repo: switch to actions based stale bot #14335
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file was deleted.
Oops, something went wrong.
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,38 @@ | ||
| on: | ||
| schedule: | ||
| - cron: '0 * * * *' | ||
|
|
||
| jobs: | ||
| Prune Stale: | ||
| runs-on: ubuntu-latest | ||
|
|
||
| steps: | ||
| - name: Prune Stale | ||
| uses: actions/stale@v3.0.14 | ||
| with: | ||
| repo-token: ${{ secrets.GITHUB_TOKEN }} | ||
| # Different amounts of days for issues/PRs are not currently supported but there is a PR | ||
| # open for it: https://github.com/actions/stale/issues/214 | ||
| days-before-stale: 30 | ||
| days-before-close: 7 | ||
| stale-issue-message: > | ||
| This issue has been automatically marked as stale because it has not had activity in the | ||
| last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity | ||
| occurs. Thank you for your contributions. | ||
| close-issue-message: > | ||
| This issue has been automatically closed because it has not had activity in the | ||
| last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted" or "no stalebot". | ||
| Thank you for your contributions. | ||
| stale-pr-message: > | ||
| This pull request has been automatically marked as stale because it has not had | ||
| activity in the last 30 days. It will be closed in 7 days if no further activity occurs. Please | ||
| feel free to give a status update now, ping for review, or re-open when it's ready. | ||
| Thank you for your contributions! | ||
| close-pr-message: > | ||
| This pull request has been automatically closed because it has not had | ||
| activity in the last 37 days. Please feel free to give a status update now, ping for review, or re-open when it's ready. | ||
| Thank you for your contributions! | ||
| stale-issue-label: 'stale' | ||
| exempt-issue-labels: 'no stalebot,help wanted' | ||
| stale-pr-label: 'stale' | ||
| exempt-pr-labels: 'no stalebot' | ||
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.
very belated question, I think if we split this into stale_prs.yaml and stale_issues.yaml I think we could reinstate the tighter stale tagging on PRs. Think it's worth it? If so I'm happy to give it a try.