Introduce reusable workflow to close stale issues #19
Conversation
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
This workflow automatically closes inactive issues after a configurable period. Issues are marked with the `stale` label upon closing. Co-authored-by: Jolien Trog <jolien.trog@icinga.com>
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.
This workflow automatically closes inactive issues after a configurable period, which is 5 years of inactivity by default.
Issues are marked with the
stalelabel upon closing.If the workflow closes an issue that should remain open,
the issue must be manually reopened and the
stalelabel removed to prevent it from being reprocessed.The following exceptions apply to the workflow:
ref/IPorref/NCare never closedThe workflow attempts to close ~5 issues per run.
The underlying action works with a credit of GitHub API operations instead of specific issue limits,
so the actual number of issues closed may vary slightly depending on issue state and operations performed.
closes #4