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.

• Not having all the items checked will fail the build, but it won't prevent merging.
• The build doesn't auto-run when the opening comment changes, so it'll need to be re-run manually.
• It's not really enforcement since items can be removed or falsely checked.

Honestly, I think this work is a bit premature. Our process should be discussed, agreed upon, and documented in CONTRIBUTING.md before we automate it. Having an assigned milestone and a test suite issue are requirements (recommendations?) that are not currently documented. Linking an issue is only mentioned as something that should be done if there is an issue that the PR resolves. Let's start by documenting what we want, then add automation where it makes sense.

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.

Honestly, I think this work is a bit premature. Our process should be discussed, agreed upon, and documented in CONTRIBUTING.md before we automate it. Having an assigned milestone and a test suite issue are requirements (recommendations?) that are not currently documented. Linking an issue is only mentioned as something that should be done if there is an issue that the PR resolves. Let's start by documenting what we want, then add automation where it makes sense. - @jdesrosiers

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.

Closing per #1069 (comment)