[airavata-custos] branch master updated: Adding .github folder to format issues and pull requests

[sm...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

smarru pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/airavata-custos.git


The following commit(s) were added to refs/heads/master by this push:
     new d30d3e2  Adding .github folder to format issues and pull requests
d30d3e2 is described below

commit d30d3e2f788165cc00e0ef084e1d5958cb8d3029
Author: Suresh Marru <sm...@apache.org>
AuthorDate: Sat May 2 16:02:58 2020 -0400

    Adding .github folder to format issues and pull requests
---
 .github/PULL_REQUEST_TEMPLATE.md | 39 +++++++++++++++++++++++++++++++++++++++
 1 file changed, 39 insertions(+)

diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
new file mode 100644
index 0000000..2925d11
--- /dev/null
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -0,0 +1,39 @@
+<!-- Thank you for your contribution to Apache Airavata!
+
+     Please file this form by replacing the Markdown comments
+     with your text. If a section needs no action - remove it.
+
+     Also remember, that Airavata uses the Review-Then-Commit (RTC) model
+     of code collaboration. Positive feedback is represented +1 from committers
+     and negative is a -1. The -1 also means veto, and needs to be addressed
+     to proceed. Once there are no objections, the PR can be merged by a
+     airavata committer.
+-->
+## Overview
+<!--- Provide a concise summary of your changes in the Title -->
+
+## Description
+<!--- Provide a detailed description of your changes. -->
+<!--- Include details of what problem you are solving-->
+
+## Testing recommendations
+
+<!-- Describe how we can test your changes.
+     Does it provides any behaviour that the end users
+     could notice? -->
+
+## Related Issues or Pull Requests
+
+<!-- If your changes affects multiple components in different
+     repositories please put links to those issues or pull requests here.  -->
+     
+## Types of changes
+<!--- What types of changes does your code introduce? Use `x` in all the boxes that apply: -->
+- [ ] Bug fix (generally a non-breaking change which closes an issue).
+- [ ] Enhancement or new feature (adds new functionality).
+- [ ] Breaking change (a bug fix or enhancement which changes existing behavior).
+
+## Checklist
+
+- [ ] Code is written and works correctly
+- [ ] Changes are covered by tests
\ No newline at end of file