-
-
Notifications
You must be signed in to change notification settings - Fork 10.2k
Add flowchart for managing ready-to-merge PRs #8627
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
Conversation
I'd say the stuff about the driver should be a separate pull request. It's useful, but it really distracts from the added diagram. |
Makes sense! Removed for now. |
I don't mean to be bikeshedding here, but the "Modify and push" text doesn't have a white background (like "Push the button" and unlike "Yes"), so the "a" in "and" seems a little too close to the line. Is it possible to make the text background white or is it intentionally this way? Disclaimer: I don't know anything about rules for diagrams 😅 |
- Add flowchart for handling ready-to-merge pull requests - Add diagram guidelines Many thanks to Sean Molenaar for the idea and initial version of the chart. CC: Sean Molenaar <smillernl@me.com>
@nandahkrishna Fixed, thanks! And yes, that’s exactly the kind of feedback I meant to solicit ❤️ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The diagram looks good to me. If you wanted to reduce the complexity a little bit, you could probably combine the "Does it say bottle :unneeded
?" and "Rebuild bottles afterwards?" questions into e.g. "Are there bottles that need to be rebuilt?". The benefit here would be to simplify the diagram a little, but I don't think that's necessary.
I don't think it's really clear how to answer this question without the explicit “check for |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, thanks for this @claui and all the help @SMillerDev and others.
Thank you all for the thorough review and helpful feedback @nandahkrishna @Rylan12 @SMillerDev @MikeMcQuaid @reitermarkus! |
Thanks @claui! Would be good to fix that if possible. |
brew style
with your changes locally?brew tests
with your changes locally?This documentation PR adds a flowchart and a diagram guideline.
Flowchart for managing ready-to-merge PRs
A flowchart can be a helpful addition to a complex decision tree.
Many thanks to @SMillerDev for the idea and initial version of the chart.
New diagram guideline
Looks like this is the first diagram in the Homebrew documentation so it’s a good time for a little guideline, too.
Pinging @Homebrew/tsc but feedback welcome from everyone, of course.