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-kogito-examples.git
The following commit(s) were added to refs/heads/main by this push:
new bb5164a95 NO_ISSUE: Fix outdated pull request template (#2176)
bb5164a95 is described below
commit bb5164a9553231725d8aa024018a81afbc080dc7
Author: Dominik Hanák <[email protected]>
AuthorDate: Wed Feb 18 12:26:33 2026 +0100
NO_ISSUE: Fix outdated pull request template (#2176)
---
.github/pull_request_template.md | 87 ++--------------------------------------
1 file changed, 3 insertions(+), 84 deletions(-)
diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
index e3ac70c34..ec58363d8 100644
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -2,91 +2,10 @@ Many thanks for submitting your Pull Request :heart:!
Please make sure that your PR meets the following requirements:
-**WARNING! Please make sure you are opening your PR against `main` branch!**
-
- [ ] You have read the [contributors
guide](https://github.com/apache/incubator-kie-kogito-runtimes#contributing-to-kogito)
-- [ ] Pull Request title is properly formatted: `KOGITO-XYZ Subject`
-- [ ] Pull Request title contains the target branch if not targeting main:
`[0.9.x] KOGITO-XYZ Subject`
-- [ ] Pull Request contains link to the JIRA issue
+- [ ] Pull Request title is properly formatted: `ISSUE-XYZ: <PR Title>`
+- [ ] Pull Request title contains the target branch if not targeting main:
`[10.0.x] ISSUE-XYZ <PR Title>`
+- [ ] Pull Request contains link to the GitHub issue
- [ ] Pull Request contains link to any dependent or related Pull Request
- [ ] Pull Request contains description of the issue
- [ ] Pull Request does not include fixes for issues other than the main ticket
-
-<details>
-<summary>
-How to replicate CI configuration locally?
-</summary>
-
-Build Chain tool does "simple" maven build(s), the builds are just Maven
commands, but because the repositories relates and depends on each other and
any change in API or class method could affect several of those repositories
there is a need to use [build-chain
tool](https://github.com/kiegroup/github-action-build-chain) to handle cross
repository builds and be sure that we always use latest version of the code for
each repository.
-
-[build-chain tool](https://github.com/kiegroup/github-action-build-chain) is a
build tool which can be used on command line locally or in Github Actions
workflow(s), in case you need to change multiple repositories and send multiple
dependent pull requests related with a change you can easily reproduce the same
build by executing it on Github hosted environment or locally in your
development environment. See [local
execution](https://github.com/kiegroup/github-action-build-chain#local-ex [...]
-</details>
-
-<details>
-<summary>
-How to retest this PR or trigger a specific build:
-</summary>
-
-- for <b>pull request checks</b>
- Please add comment: <b>Jenkins retest this</b>
-
-- for a <b>specific pull request check</b>
- Please add comment: <b>Jenkins (re)run [kogito-examples] tests</b>
-
-- for <b>quarkus branch checks</b>
- Run checks against Quarkus current used branch
- Please add comment: <b>Jenkins run quarkus-branch</b>
-
-- for a <b>quarkus branch specific check</b>
- Run checks against Quarkus current used branch
- Please add comment: <b>Jenkins (re)run [kogito-examples] quarkus-branch</b>
-
-- for <b>quarkus main checks</b>
- Run checks against Quarkus main branch
- Please add comment: <b>Jenkins run quarkus-main</b>
-
-- for a <b>specific quarkus main check</b>
- Run checks against Quarkus main branch
- Please add comment: <b>Jenkins (re)run [kogito-examples] quarkus-main</b>
-
-- for <b>quarkus lts checks</b>
- Run checks against Quarkus lts branch
- Please add comment: <b>Jenkins run quarkus-lts</b>
-
-- for a <b>specific quarkus lts check</b>
- Run checks against Quarkus lts branch
- Please add comment: <b>Jenkins (re)run [kogito-examples] quarkus-lts</b>
-
-- for <b>native checks</b>
- Run native checks
- Please add comment: <b>Jenkins run native</b>
-
-- for a <b>specific native check</b>
- Run native checks
- Please add comment: <b>Jenkins (re)run [kogito-examples] native</b>
-
-- for <b>native lts checks</b>
- Run native checks against quarkus lts branch
- Please add comment: <b>Jenkins run native-lts</b>
-
-- for a <b>specific native lts check</b>
- Run native checks against quarkus lts branch
- Please add comment: <b>Jenkins (re)run [kogito-examples] native-lts</b>
-
-</details>
-
-<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>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
