PULL_REQUEST_TEMPLATE: Add a checklist item for brew man

[issyl0]

• Have you followed the guidelines in our Contributing document?
• Have you checked to ensure there aren't other open Pull Requests for the same change?
• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your changes? Here's an example.
• Have you successfully run brew style with your changes locally?
• Have you successfully run brew tests with your changes locally?
• Have you successfully run brew man locally and committed any changes?

---

• I've been changing command flags recently. I always forget to run brew man, then I feel bad about causing red CI on my PRs. This has happened to others too, so make brew man more obvious as a thing that one should check.

[maxim-belkin]

👍 from me!

[claui]

No strong opinion about that extra item but definitely 👍 if it makes you feel better @issyl0.

Regardless: let’s aim to create an environment where no one has to feel bad about red tests, ever.

You’re an amazing person and your contributions are 💯, no matter the colour it took for them to be shipped!

[MikeMcQuaid]

Thanks for the PR, agreed. I'm almost wondering whether stuff like this could be autorun and either committed to your PR or committed to a new PR/master and our release tooling checks that it's not outdated 🤔

[vitorgalvao]

I'm almost wondering whether stuff like this could be autorun and either committed to your PR or committed to a new PR/master and our release tooling checks that it's not outdated

On homebrew-cask-fonts we have a GitHub action that runs weekly and submits a PR.

So we could have a daily action that runs brew man and commits or sends a PR if there were any changes. Or have the action run after every PR merge. Either way, I’m confident it’s doable.