This is an automated email from the ASF dual-hosted git repository.
orpiske pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/main by this push:
new 4a38f3d2448 (chores) camel 4: adjust the contribution template to help
users identify the correct branch
4a38f3d2448 is described below
commit 4a38f3d2448bc18371cfef0850c5be4b82367060
Author: Otavio Rodolfo Piske <[email protected]>
AuthorDate: Thu Jan 12 11:42:50 2023 +0100
(chores) camel 4: adjust the contribution template to help users identify
the correct branch
---
.github/pull_request_template.md | 40 ++++++++++++++++++++++++++++++++--------
1 file changed, 32 insertions(+), 8 deletions(-)
diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
index fd6280fa426..e057a589e7c 100644
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -1,9 +1,33 @@
-<!-- Uncomment and fill this section if your PR is not trivial
-- [ ] Make sure there is a [JIRA
issue](https://issues.apache.org/jira/browse/CAMEL) filed for the change
(usually before you start working on it). Trivial changes like typos do not
require a JIRA issue. Your pull request should address just this issue,
without pulling in other changes.
-- [ ] Each commit in the pull request should have a meaningful subject line
and body.
-- [ ] If you're unsure, you can format the pull request title like
`[CAMEL-XXX] Fixes bug in camel-file component`, where you replace `CAMEL-XXX`
with the appropriate JIRA issue.
-- [ ] Write a pull request description that is detailed enough to understand
what the pull request does, how, and why.
-- [ ] Run `mvn clean install -Psourcecheck` in your module with source check
enabled to make sure basic checks pass and there are no checkstyle violations.
A more thorough check will be performed on your pull request automatically.
-Below are the contribution guidelines:
-https://github.com/apache/camel/blob/main/CONTRIBUTING.md
+# Description
+
+<!--
+- Write a pull request description that is detailed enough to understand what
the pull request does, how, and why.
-->
+
+# Target
+
+- [ ] I checked that the commit is targeting the correct branch (note that
Camel 3 uses `camel-3.x`, whereas Camel 4 uses the `main` branch)
+
+# Tracking
+- [ ] If this is a large change, bug fix, or code improvement, I checked there
is a [JIRA issue](https://issues.apache.org/jira/browse/CAMEL) filed for the
change (usually before you start working on it).
+
+<!--
+# *Note*: trivial changes like, typos, minor documentation fixes and other
small items do not require a JIRA issue. In this case your pull request should
address just this issue, without pulling in other changes.
+-->
+
+# Apache Camel coding standards and style
+
+- [ ] I checked that each commit in the pull request has a meaningful subject
line and body.
+
+<!--
+If you're unsure, you can format the pull request title like `[CAMEL-XXX]
Fixes bug in camel-file component`, where you replace `CAMEL-XXX` with the
appropriate JIRA issue.
+-->
+
+- [ ] I formatted the code using `mvn -Pformat,fastinstall install && mvn
-Psourcecheck`
+
+<!--
+You can run the aforementioned command in your module so that the build
auto-formats your code and the source check verifies that is complies with our
coding style. This will also be verified as part of the checks and your PR may
be rejected if the checkstyle does not pass.
+
+You can learn more about the contribution guidelines at
https://github.com/apache/camel/blob/main/CONTRIBUTING.md
+-->
+
