Draft
Conversation
Signed-off-by: Craig Osterhout <craig.osterhout@docker.com>
✅ Deploy Preview for docsdocker ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
Author
|
/review |
Contributor
There was a problem hiding this comment.
Assessment: 🟢 APPROVE
This workflow configuration looks good. The debug mode is intentionally enabled as documented in the PR description, which is a safe approach for initial deployment.
One minor consideration for future optimization: the operations-per-run: 30 limit processes up to 30 items per day. If the repository accumulates many stale issues/PRs, you may want to increase this value (e.g., 100-300) to ensure timely processing. The current value is the recommended default and should work fine for most cases.
Signed-off-by: Craig Osterhout <craig.osterhout@docker.com>
Signed-off-by: Craig Osterhout <craig.osterhout@docker.com>
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
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.
Description
This PR adds a GitHub Actions workflow to automatically mark and close stale issues and PRs, helping maintainers focus on active items. The old app/bot stopped working around mid 2025 and was disabled. This reimplements it using a GitHub Action with additional slash command functionality.
Timeframes
Exempt Labels
Issues and PRs with any of these labels will never be marked as stale:
kind/help wantedstatus/need-more-infostatus/needs-analysislifecycle/frozenHow to Keep Issues/PRs Active
To prevent an issue or PR from being marked as stale or closed:
Anyone can:
/lifecycle active- removes the stale label via slash commandMaintainers can also:
3. Use
/lifecycle frozen- prevents the issue/PR from ever being marked stale4. Add exempt labels - manually apply one of the labels listed above
5. Make any update - editing the description, adding labels, or any activity resets the timer
Slash Commands
The workflow supports these lifecycle commands (comment them on any issue/PR):
/lifecycle active/lifecycle frozen/lifecycle stale/remove-lifecycle frozen/remove-lifecycle staleCommands respond with a 👍 reaction when successful, 👎 when permission is denied.
Messages
When marked as stale, issues and PRs receive a friendly comment explaining:
/lifecycle active/lifecycle frozenDebug Mode
The workflow is currently set to debug mode for both components:
Stale action (
debug-only: true):Lifecycle commands (
DEBUG_ONLY: 'true'):