chore: add stale workflow for issues and PRs#487
Merged
marandaneto merged 2 commits intomainfrom Apr 13, 2026
Merged
Conversation
dustinbyrne
approved these changes
Apr 13, 2026
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
2 participants
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.
💡 Motivation and Context
Some client-library repos do not have the stale workflow that posthog-js already uses, so stale issues and PRs are not being cleaned up consistently across the org.
💚 How did you test it?
Reviewed the workflow YAML and verified it configures
actions/stale@v10for both issues and PRs.📝 Checklist
If releasing new changes
pnpm changesetto generate a changeset filereleaselabel to the PR