-
Notifications
You must be signed in to change notification settings - Fork 848
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
Stale issue/pr action #4625
Stale issue/pr action #4625
Conversation
Where do they put the logs? |
They live in the actions interface. You need to add a key to the repo to turn them on. I'd like to configure the messages first, then we should be safe to merge this, watch the log output as it runs (once every 8 hours) and then make some tweaks. |
Preview documentation changes for this PR: https://eui.elastic.co/pr_4625/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Interested in seeing the statistics in the end.
I have added a duplicate of this action on a shorter timer over in our gatsby-starter https://github.com/elastic/gatsby-eui-starter/actions/workflows/stale.yml Once I see it successfully run and generating logs I'll merge this PR so we can see some dry-run stats for our meeting. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool, let's try it out
Preview documentation changes for this PR: https://eui.elastic.co/pr_4625/ |
Here's an example of the logs generated for https://github.com/elastic/gatsby-eui-starter/runs/2061211848?check_suite_focus=true I can see that it successfully ran in debug mode and took no action on the issues/prs. I'm gonna take that as reason this is safe to merge. |
Preview documentation changes for this PR: https://eui.elastic.co/pr_4625/ |
Summary
Adds a Github action that checks for stale issues and PRs using https://github.com/actions/stale, which is Github's officially supported action for stale checks. To run this in a dry run mode, I've turned on Github logging for the repo, and set
debug-only: true
for the action. The docs on https://github.com/actions/stale#debugging suggest this means the action will not be run, and only be logged. This should allow us to watch how this would effect our repo.Checklist