This is an automated email from the ASF dual-hosted git repository.
tzimanyi pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/incubator-kie-drools.git
The following commit(s) were added to refs/heads/main by this push:
new 6f431492fd [incubator-kie-drools#5728] Update PR template (#5729)
6f431492fd is described below
commit 6f431492fde647b8e3ad572c943dce000c98cdb5
Author: Toshiya Kobayashi <[email protected]>
AuthorDate: Mon Feb 26 17:58:17 2024 +0900
[incubator-kie-drools#5728] Update PR template (#5729)
---
.github/pull_request_template.md | 97 ++++------------------------------------
1 file changed, 9 insertions(+), 88 deletions(-)
diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
index d38feb205b..aa9df9aab7 100644
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -1,16 +1,15 @@
**Thank you for submitting this pull request**
-**NOTE!:** Double check the target branch for this PR.
+**NOTE!:** Double-check the target branch for this PR.
The default is `main` so it will target Drools 8 / Kogito.
-If this PR is not strictly related to drools and kogito project in
`drools.git`, it should probably target `7.x`as a branch
**Ports** If a forward-port or a backport is needed, paste the forward port PR
here
-[link](https://www.example.com)
+* [link](https://www.example.com)
-**JIRA**: _(please edit the JIRA link if it exists)_
+**Issue**: _(please edit the GitHub Issues link if it exists)_
-[link](https://www.example.com)
+* [link](https://www.example.com)
**referenced Pull Requests**: _(please edit the URLs of referenced
pullrequests if they exist)_
@@ -33,90 +32,12 @@ Build Chain tool does "simple" maven build(s), the builds
are just Maven command
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 <b>pull request and downstream checks</b>
+ - Push a new commit to the PR. An empty commit would be enough.
-- for a <b>specific pull request check</b>
- Please add comment: <b>Jenkins (re)run
[drools|kogito-runtimes|kogito-apps|kogito-examples] tests</b>
-
-- for a <b>full downstream build</b>
- - for <b>jenkins</b> job: please add comment: <b>Jenkins run fdb</b>
+- for a <b>full downstream build</b>
- for <b>github actions</b> job: add the label `run_fdb`
-- <b>a compile downstream build</b> please add comment: <b>Jenkins run cdb</b>
-
-- <b>an upstream build</b> please add comment: <b>Jenkins run upstream</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
[drools|kogito-runtimes|kogito-apps|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
[drools|kogito-runtimes|kogito-apps|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
[drools|kogito-runtimes|kogito-apps|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
[drools|kogito-runtimes|kogito-apps|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
[drools|kogito-runtimes|kogito-apps|kogito-examples] native-lts</b>
+- for <b>Jenkins PR check only</b>
+ - If you are an ASF committer for KIE podling, login to Jenkins
(https://ci-builds.apache.org/job/KIE/job/drools/), go to the specific PR job,
and click on `Build Now` button.
</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>
-
-<!-- TODO to uncomment if activating the quarkus-3 rewrite PR job -->
-<!-- <details>
-<summary>
-Quarkus-3 PR check is failing ... what to do ?
-</summary>
-The Quarkus 3 check is applying patches from the
`.ci/environments/quarkus-3/patches`.
-
-The first patch, called `0001_before_sh.patch`, is generated from Openrewrite
`.ci/environments/quarkus-3/quarkus3.yml` recipe. The patch is created to speed
up the check. But it may be that some changes in the PR broke this patch.
-No panic, there is an easy way to regenerate it. You just need to comment on
the PR:
-```
-jenkins rewrite quarkus-3
-```
-and it should, after some minutes (~20/30min) apply a commit on the PR with
the patch regenerated.
-
-Other patches were generated manually. If any of it fails, you will need to
manually update it... and push your changes.
-</details> -->
\ No newline at end of file
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
