Repository: apex-site Updated Branches: refs/heads/master 693634e99 -> a1d111287
Contributors to add JIRA number in PR title. This closes #49 Project: http://git-wip-us.apache.org/repos/asf/apex-site/repo Commit: http://git-wip-us.apache.org/repos/asf/apex-site/commit/a1d11128 Tree: http://git-wip-us.apache.org/repos/asf/apex-site/tree/a1d11128 Diff: http://git-wip-us.apache.org/repos/asf/apex-site/diff/a1d11128 Branch: refs/heads/master Commit: a1d111287680f33296a2143888369e34e2a74981 Parents: 693634e Author: Thomas Weise <[email protected]> Authored: Wed Aug 31 13:54:17 2016 -0700 Committer: David Yan <[email protected]> Committed: Wed Aug 31 14:02:38 2016 -0700 ---------------------------------------------------------------------- src/md/contributing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/apex-site/blob/a1d11128/src/md/contributing.md ---------------------------------------------------------------------- diff --git a/src/md/contributing.md b/src/md/contributing.md index d542216..2df4480 100644 --- a/src/md/contributing.md +++ b/src/md/contributing.md @@ -44,7 +44,7 @@ Creating a local branch that tracks a remote makes pull easier (no need to speci 1. When adding new files, please include the Apache v2.0 license header. - From the top level directory, run `mvn license:check -Dlicense.skip=false` to check correct header formatting. - Run `mvn license:format -Dlicense.skip=false` to automatically add the header when missing. -1. Once your feature is complete, submit the pull request on github against `master`. +1. Once your feature is complete, submit the pull request on github against `master`. Use the JIRA number (e.g. APEXCORE-123) as prefix in the pull request title. This will ensure the information is attached to the JIRA ticket automatically. 1. If you want specific people to review your pull request, use the `@` notation in Github comments to mention that user, and request that he/she reviews your changes. 1. Check the status of the pull request and ensure the Travis CI build is successful. If not, inspect the linked build log for details. - If build fails due to license headers, follow instructions above.
