jomarko opened a new pull request, #1810: URL: https://github.com/apache/incubator-kie-kogito-images/pull/1810
This a partial fix for the issue https://github.com/apache/incubator-kie-issues/issues/1613 as we open one PR per repository. <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. --> Many thanks for submitting your Pull Request :heart:! Please make sure your PR meets the following requirements: - [ ] You have read the [contributors guide](README.md#contributing-to-kogito-images-repository) - [ ] Pull Request title is properly formatted: `[Issue XXXX] Subject` - [ ] Pull Request contains link to the JIRA issue - [ ] Pull Request contains description of the issue - [ ] Pull Request does not include fixes for issues other than the main ticket - [ ] Your feature/bug fix has a testcase that verifies it - [ ] You've tested the new feature/bug fix in an actual OpenShift cluster - [ ] You've added a [RELEASE_NOTES.md](RELEASE_NOTES.md) entry regarding this change <details> <summary> How to retest this PR or trigger a specific build: </summary> - <b>(Re)run Jenkins tests</b> Please add comment: <b>Jenkins [test|retest] this</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> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
