How to get your PR reviewed
summary
Advice centers on concrete, repeatable steps: use GitHub Actions to encode contribution rules, install the pr compliance action that guides PRs, require an issue before merging, and use a PR template filled with an SQA description. Project examples show automation tying issues to releases on a repo with about 66 contributors and ~600 stars, and maintainers report fewer irrelevant PRs and faster merges once the bot and templates are in place.
AI-written summary · about
chapters (11)
- 0:00Start
- 1:35GitHub
- 2:23Developer Advocate Brian Douglas
- 2:41The path into open source is broken
- 3:00If you don't got sauce, then you lost
- 3:28How do I get my PR reviewed?
- 3:55Talk first, commit later
- 5:11Build trust
- 6:15apps/catsup-app
- 7:46Abide by the rules
- 13:03Provide Value
related talks
18mHow to get your pull request merged
21mHow To Make AI-Assisted OSS Contributions Review-Ready
32mContributing to Open Source: A Guide
30mWhy & how you can be reviewing OSS PRs
57mA Meritocracy of Pull Requests
15mReviewing PRS
10mDemystifying Contributing to Open Source
32mYour First Open-Source Contribution