Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sync main branch with Apache main branch #2

Merged
merged 8 commits into from
Jan 22, 2024

Conversation

rgdoliveira
Copy link
Member

Many thanks for submitting your Pull Request ❤️!

Please make sure your PR meets the following requirements:

  • You have read the contributors guide
  • Pull Request title is properly formatted: [KOGITO|RHPAM-XYZ] 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 entry regarding this change
How to retest this PR or trigger a specific build:
  • (Re)run Jenkins tests
    Please add comment: Jenkins [test|retest] this

  • Prod tests
    Please add comment: Jenkins (re)run [prod|Prod|PROD]

How to backport a pull request to a different branch?

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.

asf-ci-kie and others added 8 commits January 22, 2024 08:29
* Add apache license headers

* github.com/kiegroup -> github.com/apache/incubator-kie-

* trigger build

* trigger build

* trigger build

* keep kie-cloud-tools link

* Add header to new files since PR was opened

* 755 permission

* restore 755 permission

* restore 755 permission 2
)

* Remove MongoDB leftovers duo to ASF restrictions

Signed-off-by: Ricardo Zanini <[email protected]>

* Removing composer references on Infinispan and MongoDB

Signed-off-by: Ricardo Zanini <[email protected]>

* Remove Inifinispan leftovers

Signed-off-by: Ricardo Zanini <[email protected]>

---------

Signed-off-by: Ricardo Zanini <[email protected]>
@rgdoliveira rgdoliveira merged commit 2674869 into kiegroup:main Jan 22, 2024
3 checks passed
akumar074 pushed a commit to akumar074/kogito-images that referenced this pull request Feb 29, 2024
[1.13.x-blue-next][SRVLOGIC-158] - Dynamic resources script is readin…
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants