Skip to content
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

Add GitHub action to mark inactive issues and PRs as stale #9

Merged
merged 1 commit into from
Sep 25, 2022

Conversation

chriszarate
Copy link
Member

Description

This pull request introduces a GitHub action that runs daily and will automatically mark inactive issues and PRs as stale. Keeping issues and pull requests manageable and actionable is important for a codebase's health.

The default behavior of this action will mark issues and pull requests as stale after 60 days of inactivity, by adding a label of [Status] Stale and leaving an explanatory comment (example). If another 7 days of inactivity pass, it will be labeled [Status] Autoclosed and closed. (It can always be reopened, which resets the clock.)

This action ignores issues and PRs with the following labels:

  • [Pri] Critical
  • [Status] Keep
  • dependencies (ensures that Dependabot pull requests are not marked as stale or closed)

You can easily customize the time periods used for marking an issue stale or autoclosing. Consult the documentation for details on providing overrides.

Feel free to close this pull request if it does not suit your project's needs or workflows. If you would consider merging this pull request if the action were improved in some way, please open an issue or pull request to let us know.

Deploy Notes

Upon merging, this action will run at about midnight UTC. Issues and pull requests that already meet the stale threshold will be immediately marked stale, but will not be autoclosed until an additional 7 days of inactivity pass.

@chriszarate chriszarate merged commit f392f49 into trunk Sep 25, 2022
@chriszarate chriszarate deleted the add/stale-issue-pr-bot branch September 25, 2022 17:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant