-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Switch to GitHub Action's stale bot #20475
Labels
T: task
An enhancement to the software.
Comments
Make sure we only label PRs, not all issues. Also, I might suggest that we give more than 1 day to close after being stale. Maybe 3 so we don't lose things on weekends. That might be a good compromise for when this action runs on a Friday. |
milljm
added a commit
to milljm/moose
that referenced
this issue
Mar 7, 2022
milljm
added a commit
to milljm/moose
that referenced
this issue
Mar 7, 2022
Label PRs older than 30 days with no activity as stale. Close PRs labeled as stale if they continue to not have activity after 3 days. Closes idaholab#20475
milljm
added a commit
to milljm/moose
that referenced
this issue
Mar 7, 2022
Label PRs older than 30 days with no activity as stale. Close PRs labeled as stale if they continue to not have activity after 3 days. Closes idaholab#20475
cticenhour
added a commit
to cticenhour/moose
that referenced
this issue
Mar 9, 2022
cticenhour
added a commit
to cticenhour/moose
that referenced
this issue
Mar 14, 2022
Disables issue checking, and increases operations per run to exceed the running max average of PRs (~75)
cticenhour
added a commit
to cticenhour/moose
that referenced
this issue
Mar 14, 2022
Up to 3 operations are performed for a newly stale PR (label, message, check for closure), with 1 being performed to check to see if a stale PR should be closed. This sets the operation limit high enough to capture ~33 newly stale PRs, which should be more than enough for now.
cticenhour
added a commit
to cticenhour/moose
that referenced
this issue
Mar 14, 2022
Relevant to our current configuration: - Introduces more readable and colorful log output. - Updates Node.js runtime to 16, as 12 will reach end of life on 30 Apr 2022.
Merged
cticenhour
added a commit
to cticenhour/moose
that referenced
this issue
Mar 14, 2022
Relevant to our current configuration: - Introduces more readable and colorful log output. - Updates Node.js runtime to 16, as 12 will reach end of life on 30 Apr 2022.
cticenhour
added a commit
to cticenhour/moose
that referenced
this issue
Mar 14, 2022
Relevant to our current configuration: - Introduces more readable and colorful log output. - Updates Node.js runtime to 16, as 12 will reach end of life on 30 Apr 2022.
cticenhour
added a commit
to cticenhour/moose
that referenced
this issue
Mar 15, 2022
This is based on discussion from one of the stalebot developers at: actions/stale#688 Also adjusts the PR message to contain our set days before stale and closure, for developer information.
permcody
added a commit
that referenced
this issue
Mar 15, 2022
Disable issue checking in stalebot (#20475)
grmnptr
pushed a commit
to grmnptr/moose
that referenced
this issue
Mar 29, 2022
Up to 3 operations are performed for a newly stale PR (label, message, check for closure), with 1 being performed to check to see if a stale PR should be closed. This sets the operation limit high enough to capture ~33 newly stale PRs, which should be more than enough for now.
grmnptr
pushed a commit
to grmnptr/moose
that referenced
this issue
Mar 29, 2022
Relevant to our current configuration: - Introduces more readable and colorful log output. - Updates Node.js runtime to 16, as 12 will reach end of life on 30 Apr 2022.
grmnptr
pushed a commit
to grmnptr/moose
that referenced
this issue
Mar 29, 2022
This is based on discussion from one of the stalebot developers at: actions/stale#688 Also adjusts the PR message to contain our set days before stale and closure, for developer information.
cticenhour
added a commit
to cticenhour/moose
that referenced
this issue
Apr 5, 2022
cticenhour
added a commit
to cticenhour/moose
that referenced
this issue
Apr 5, 2022
…idaholab#20475) Increase days before PR close with stale bot to 7, and increase days before PR stale determination to 100
cticenhour
added a commit
to cticenhour/moose
that referenced
this issue
Jan 9, 2023
Remove old stalebot configuration file Refs idaholab#20475
cticenhour
added a commit
to cticenhour/moose
that referenced
this issue
Sep 6, 2023
…tale action to version 8 Refs idaholab#20475
oanaoana
pushed a commit
to oanaoana/moose
that referenced
this issue
Oct 19, 2023
…tale action to version 8 Refs idaholab#20475
oanaoana
pushed a commit
to oanaoana/moose
that referenced
this issue
Nov 7, 2023
…tale action to version 8 Refs idaholab#20475
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Reason
ProBot Stale Bot is no more.
Design
Following the instructions here: https://github.com/marketplace/actions/close-stale-issues, configure idaholab/moose to use this new implementation of stale issue closures.
Impact
Label issues older than 30 days as Stale, and then close them 1 day later.
The text was updated successfully, but these errors were encountered: