-
Notifications
You must be signed in to change notification settings - Fork 29.1k
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
Use GitHub Actions for writing a stale action #29232
Comments
Configs discussed in #28798:
To avoid too many stale notifications at once, use |
Initially, I would go with a longer stale period. Let's say 90 to 120 days. |
The
The idea is post stale message every We can update |
I'm still +1 on this. |
@trivikr I think you should go ahead and open a PR |
I just got access to GitHub Actions Beta, and will experiment with it over the Labour Day weekend 😄 |
I couldn't play with GitHub Actions during Labour Day weekend, and friends planned another trip this weekend. |
I'll be playing with GitHub actions over the weekend of 09/14 |
Update: GitHub stale action is pretty new, and will need some time to get stable. For example, the support for exempt labels was added on Aug 27 in actions/stale#11 |
In Node.js core, we tried writing CI with GitHub Actions in #29193 |
GitHub just added a new workflow editor for Actions |
I'm going to close this because I don't think there's support for it. But if someone thinks I'm wrong and wants to try to work something up, please re-open or leave a comment (or jump right to the open-a-pull-request option). |
Is your feature request related to a problem? Please describe.
This came up in #28798 (comment) where we were planning to use stale bot
Describe the solution you'd like
Use GitHub Actions for writing a stale action (example)
Describe alternatives you've considered
Follow #28798 (comment)
The text was updated successfully, but these errors were encountered: