This is an automated email from the ASF dual-hosted git repository. kaxilnaik pushed a commit to branch v1-10-test in repository https://gitbox.apache.org/repos/asf/airflow.git
commit 25e0e2617c536d4ac9128cbace381082441a3db0 Author: Tomek Urbaszek <turbas...@gmail.com> AuthorDate: Tue Jul 21 12:18:07 2020 +0200 Simplify pull request template (#9896) Remove the checklist of always checked points. (cherry picked from commit 7dd5c11f966df0cb20b7503be3438e19248e66ea) --- .github/PULL_REQUEST_TEMPLATE.md | 27 ++++++++++++++++++++------- 1 file changed, 20 insertions(+), 7 deletions(-) diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md index 64625e4..1e3c23d 100644 --- a/.github/PULL_REQUEST_TEMPLATE.md +++ b/.github/PULL_REQUEST_TEMPLATE.md @@ -1,10 +1,23 @@ -- [ ] Description above provides context of the change -- [ ] Commit message contains [\[AIRFLOW-XXXX\]](https://issues.apache.org/jira/browse/AIRFLOW-XXXX) or `[AIRFLOW-XXXX]` for document-only changes -- [ ] Unit tests coverage for changes (not needed for documentation changes) -- [ ] Commits follow "[How to write a good git commit message](http://chris.beams.io/posts/git-commit/)" -- [ ] Relevant documentation is updated including usage instructions. -- [ ] I will engage committers as explained in [Contribution Workflow Example](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#contribution-workflow-example). +<!-- +Thank you for contributing! Please make sure that your code changes +are covered with tests. And in case of new features or big changes +remember to adjust the documentation. + +Feel free to ping committers for the review! + +In case of existing issue, reference it using one of the following: + +closes: #ISSUE +related: #ISSUE + +How to write a good git commit message: +http://chris.beams.io/posts/git-commit/ +--> + +--- +**^ Add meaningful description above** + +Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#pull-request-guidelines)** for more information. In case of fundamental code change, Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals)) is needed. In case of a new dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). In case of backwards incompatible changes please leave a note in [UPDATING.md](https://github.com/apache/airflow/blob/master/UPDATING.md). -Read the [Pull Request Guidelines](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#pull-request-guidelines) for more information.