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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pr automation #1072
base: main
Are you sure you want to change the base?
Pr automation #1072
Conversation
adding checklist looks 馃憤 working on enforcing next... |
can you summarize what these checklists entail, for those of us who haven't learned github workflows yet? :) |
There's some discussion in #1069 around it. It's basically a guide or reminder.
|
Honestly, I think this work is a bit premature. Our process should be discussed, agreed upon, and documented in |
As I mentioned above, there has been some discussion in issues as well as in Slack, but if you'd like official docs first that's fine. I don't think this will go stale or conflict with anything. |
I think I'd have to agree. I'm doing some work this week on community things so let's see how we go. |
@gregsdennis given the concerns from @jdesrosiers and @Relequestual (with which I think I agree), can this be closed in favor of a discussion somewhere? |
There's already discussion elsewhere, as noted in the opening comment. This PR isn't doing any harm just sitting here. This kind of automation is still something I'd like to see. It relates to repo management, like requiring an approval, which we did a few weeks ago; it's a nice to have. The only reason it's still open is that people have forgotten about it. |
I also discovered that actions can trigger from comment changes, so I might add that. |
Resolves #1069
Relates to #1070 & #1071
Happy to take opinions on the content of 馃憞. It all works pretty well, though, so I don't think I'll be changing the mechanics.