glusterfs.git/.github/PULL_REQUEST_TEMPLATE, branch v4.1.6 doc: describe how to contribute when a GitHub Pull-Request is made 2018-01-30T15:05:55+00:00 Niels de Vos ndevos@redhat.com 2018-01-22T10:08:48+00:00 6baa79b17337bb9fd8aa95e4f8c743ab4111aa75 Every now and then new contributors create a GitHub Pull-Request. We do not use those for accepting changes, and almost never check for new PRs. Redirecting contributors can be done automatically, just like we do when users create a GitHub Issue. Note that the bulk of the description comes from gluster-block. Just like most Gerrit maintained projects, it uses 'git review' and not a custom ./rfc.sh. New contributors that are familiar with Gerrit, will prefer the 'git review' approach over ./rfc.sh (which we want to deprecate or at least have it use 'git review' too). Change-Id: Ide36cbd80fdaaf238ea35ae5932a0cd21fc41f36 Updates: #381 URL: https://help.github.com/articles/creating-a-pull-request-template-for-your-repository/ Signed-off-by: Niels de Vos <ndevos@redhat.com> 
Every now and then new contributors create a GitHub Pull-Request. We do
not use those for accepting changes, and almost never check for new PRs.
Redirecting contributors can be done automatically, just like we do when
users create a GitHub Issue.

Note that the bulk of the description comes from gluster-block. Just
like most Gerrit maintained projects, it uses 'git review' and not a
custom ./rfc.sh. New contributors that are familiar with Gerrit, will
prefer the 'git review' approach over ./rfc.sh (which we want to
deprecate or at least have it use 'git review' too).

Change-Id: Ide36cbd80fdaaf238ea35ae5932a0cd21fc41f36
Updates: #381
URL: https://help.github.com/articles/creating-a-pull-request-template-for-your-repository/
Signed-off-by: Niels de Vos <ndevos@redhat.com>