Replies: 1 comment
-
|
@veroandreo wou might want to take a look at it and add it to the discussion |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I'm filing this for discussion at a PSC meeting, as a possibility for #3235.
I imagine that part of a solution could be with using a specially configured stale bot.
https://github.com/actions/stale
Even if one day, it can be used to close PRs/issues, it can be configured to not close and ping back after a time. So here are some specific configuration keys that might be interesting for us:
Remember that the message should include instructions on removing the stale label to have the timer restarted, and what label to add to exclude that issue/PR from getting stale. It's an escape strategy.
So, as for the smallest possible implementation steps that it could be split into, I imaging the following:
Beta Was this translation helpful? Give feedback.
All reactions