Skip to content

Well Formed Pull Requests

Pat Maddox edited this page Jul 8, 2015 · 5 revisions

Well-Formed Pull Requests

A well-formed pull request...

  1. is for files only within your personal sub-directory.
  2. contains a single sub-directory for that step of the challenge.
  3. contains a README.md in that sub-directory describing what you did
  4. does not contain any files unrelated to your work (tmp files, backup files, etc)
  5. is a fast-forward of master - in other words, has only unique commits and doesn't end in a merge (ideally, no merges...)

For minimal headaches when submitting pull requests, follow the suggested git workflow.

Here's how you submit a pull request via GitHub.