summaryrefslogtreecommitdiffstats
path: root/.github/PULL_REQUEST_TEMPLATE
Commit message (Collapse)AuthorAgeFilesLines
* github templates: Change to reflect the future workflowAmar Tumballi2020-02-281-33/+0
| | | | | | | | | | | * Issue template changed to remove reference to bugzilla * PR template removed. CONTRIBUTING made .md friendly (will be renamed once we shift review process) Updates: #824 Change-Id: Ifd6f93ad9b7be97d8eb950a141fe585d3e5ed021 Signed-off-by: Amar Tumballi <amar@kadalu.io>
* doc: describe how to contribute when a GitHub Pull-Request is madeNiels de Vos2018-01-301-0/+33
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>