DEV Community

Discussion on: What is the proper etiquette for declining PRs on open source projects you own?

Collapse
 
emcain profile image
Emily Cain

In addition to the excellent tips already suggested, I'd include a section in the README on "how to PR" that outlines the following:

  1. "Please only submit pull requests corresponding to an issue. Check if an issue exists for what you want to do before submitting. If it does exist, write a comment with your proposed solution and wait for my response before starting work. If an issue doesn't already exist, create one." (Paraphrase and tweak this to make sense in the context of your project)

  2. If you have a broad outline of what does and doesn't fit with where you want to go with the project, give some info on that, but emphasize that people should still use/create issues to determine if their PR is needed before doing any work.

Then don't accept any PRs that don't follow 1). If someone submits a PR with no issue attached, link them to the section of the README that explains 1) and ask them to link to a ticket before you'll look at it.