-
Notifications
You must be signed in to change notification settings - Fork 382
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
(#1754) Replace Stalebot with GitHub action #1798
Conversation
When we renamed the repository previously the stalebot stopped working on this repository, this PR re-adds the stalebot but as part of a daily GitHub action instead.
✅ Package verification completed without issues. PR is now pending human review |
Before this gets merged, we'll need to verify if GitHub actions are enabled under settings for this repository (I am currently unable to verify this). |
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.
Minor tweaks, but otherwise, this LGTM!
Co-authored-by: Paul Broadwith <pauby@users.noreply.github.com> Co-authored-by: Gary Ewan Park <gep13@gep13.co.uk>
✅ Package verification completed without issues. PR is now pending human review |
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!
✅ Package verification completed without issues. PR is now pending human review |
Co-authored-by: Paul Broadwith <pauby@users.noreply.github.com> Co-authored-by: Gary Ewan Park <gep13@gep13.co.uk>
656380d
to
b6c70b8
Compare
✅ Package verification completed without issues. PR is now pending human review |
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!
@AdmiringWorm thank for getting this switched over! |
Description
When we renamed the repository previously the stalebot
stopped working on this repository, this PR re-adds the
stalebot but as part of a daily GitHub action instead.
Motivation and Context
To automatically mark issues as stale, and close issues and pull requests automatically when they are inactive.
How Has this Been Tested?
Just a quick test on my fork of the repository to see if the issues would be marked as stale.
Screenshot (if appropriate, usually isn't needed):
Types of changes
Checklist:
Original Location
N/A