Repository: incubator-gobblin Updated Branches: refs/heads/master 381316ad9 -> c9ad0a8fc
[GOBBLIN-168] Standardize Github PR template for Gobblin Project: http://git-wip-us.apache.org/repos/asf/incubator-gobblin/repo Commit: http://git-wip-us.apache.org/repos/asf/incubator-gobblin/commit/6cd5aafb Tree: http://git-wip-us.apache.org/repos/asf/incubator-gobblin/tree/6cd5aafb Diff: http://git-wip-us.apache.org/repos/asf/incubator-gobblin/diff/6cd5aafb Branch: refs/heads/master Commit: 6cd5aafbd53057842b87d8ab555021fd1b6f0f8d Parents: 381316a Author: Abhishek Tiwari <[email protected]> Authored: Thu Jul 27 02:32:12 2017 -0700 Committer: Abhishek Tiwari <[email protected]> Committed: Thu Jul 27 02:32:12 2017 -0700 ---------------------------------------------------------------------- .github/PULL_REQUEST_TEMPLATE.md | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/incubator-gobblin/blob/6cd5aafb/.github/PULL_REQUEST_TEMPLATE.md ---------------------------------------------------------------------- diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md new file mode 100644 index 0000000..afff394 --- /dev/null +++ b/.github/PULL_REQUEST_TEMPLATE.md @@ -0,0 +1,27 @@ +Dear Gobblin maintainers, + +Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below! + + +### JIRA +- [ ] My PR addresses the following [Gobblin JIRA](https://issues.apache.org/jira/browse/GOBBLIN/) issues and references them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR" + - https://issues.apache.org/jira/browse/GOBBLIN-XXX + + +### Description +- [ ] Here are some details about my PR, including screenshots (if applicable): + + +### Tests +- [ ] My PR adds the following unit tests __OR__ does not need testing for this extremely good reason: + + +### Commits +- [ ] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "[How to write a good git commit message](http://chris.beams.io/posts/git-commit/)": + 1. Subject is separated from body by a blank line + 2. Subject is limited to 50 characters + 3. Subject does not end with a period + 4. Subject uses the imperative mood ("add", not "adding") + 5. Body wraps at 72 characters + 6. Body explains "what" and "why", not "how" +
