Disable issue checking in stalebot (#20475) #20559
Merged
Conversation
This file contains 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
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.
|
Job Documentation on 208b3e2 wanted to post the following: View the site here This comment will be updated on new commits. |
|
Job Coverage on 208b3e2 wanted to post the following: Framework coverageCoverage did not change Modules coverageCoverage did not change Full coverage reportsReports
This comment will be updated on new commits. |
permcody
approved these changes
Mar 15, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We originally thought only defining PR messages and other parameters would be enough to disable issue checks. This is not the case (as seen in our most recent action log), and does eat up our permitted number of operations without any gain. The stalebot will determine an issue is stale and attempt to apply a message and label. Since those aren't defined, it just skips. However 3 operations are still "performed".
This PR disables issue checking by setting
days-before-issue-staleto-1based on discussion from one of the stalebot developers at: actions/stale#688This PR also adjusts the PR message to contain our set days before stale and closure, for developer information.
Refs #20475