This is an automated email from the ASF dual-hosted git repository.
dhanak pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/incubator-kie-docs.git
The following commit(s) were added to refs/heads/main by this push:
new 4fec31e9d NO_ISSUE: Update pull request template (#4582)
4fec31e9d is described below
commit 4fec31e9d6b47b229d3d9a0c17d8c46ca4486ec3
Author: Dominik Hanák <[email protected]>
AuthorDate: Wed Feb 25 10:24:14 2026 +0100
NO_ISSUE: Update pull request template (#4582)
---
.github/pull_request_template.md | 34 ++++++++++++----------------------
1 file changed, 12 insertions(+), 22 deletions(-)
diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
index 35ac56981..fe08c756f 100644
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -1,27 +1,17 @@
-**Thank you for submitting this pull request**
+<!-- Please don't forget your Issue link -->
+Closes/Fixes/Resolves #ISSUE-NUMBER
-**JIRA**: _(please edit the JIRA link if it exists)_
+<!-- Please provide a short description of what this PR does -->
+**Description:**
-[link](https://www.example.com)
+<!-- Link to related PRs: -->
-**referenced Pull Requests**: _(please edit the URLs of referenced
pullrequests if they exist)_
+Please make sure that your PR meets the following requirements:
-* paste the link(s) from GitHub here
-* link 2
-* link 3 etc.
+- [ ] You have read the [contributions
doc](https://github.com/apache/incubator-kie-docs/blob/main/CONTRIBUTING.md)
+- [ ] Pull Request title is properly formatted: `Issue-XYZ Subject`
+- [ ] Pull Request title contains the target branch if not targeting main:
`[0.9.x] Issue-XYZ Subject`
+- [ ] The nav.adoc file has a link to this guide in the proper category
+- [ ] The index.adoc file has a card to this guide in the proper category,
with a meaningful description
-<details>
-<summary>
-How to backport a pull request to a different branch?
-</summary>
-
-In order to automatically create a **backporting pull request** please add one
or more labels having the following format `backport-<branch-name>`, where
`<branch-name>` is the name of the branch where the pull request must be
backported to (e.g., `backport-7.67.x` to backport the original PR to the
`7.67.x` branch).
-
-> **NOTE**: **backporting** is an action aiming to move a change (usually a
commit) from a branch (usually the main one) to another one, which is generally
referring to a still maintained release branch. Keeping it simple: it is about
to move a specific change or a set of them from one branch to another.
-
-Once the original pull request is successfully merged, the automated action
will create one backporting pull request per each label (with the previous
format) that has been added.
-
-If something goes wrong, the author will be notified and at this point a
manual backporting is needed.
-
-> **NOTE**: this automated backporting is triggered whenever a pull request on
`main` branch is labeled or closed, but both conditions must be satisfied to
get the new PR created.
-</details>
+<details>
\ No newline at end of file
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
