chore: add stalebot #3375
Merged
chore: add stalebot #3375
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
Signed-off-by: schristoff <[email protected]>
✅ Deploy Preview for zarf-docs canceled.
|
Signed-off-by: schristoff <[email protected]>
mkcp
approved these changes
Jan 6, 2025
Codecov ReportAll modified and coverable lines are covered by tests ✅ |
schristoff
added a commit
that referenced
this pull request
Jan 7, 2025
This reverts commit 79acb12.
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.
Reason:
As a smaller open source team it can be difficult without set triage people to manage the inbound requests. To keep ontop of the amount of requests I propose we start to mark issues stale after 60 days. After 70 days of no activity the issue will be closed.
Pull requests will never be closed, but marked stale after 45 days.
If an issue or PR is assigned to a milestone it will exempt from this.