Skip to content

Conversation

@dellamas
Copy link
Contributor

@dellamas dellamas commented Jun 3, 2025

Many thanks for submitting your Pull Request ❤️!

Please make sure that your PR meets the following requirements:

  • You have read the contributors guide
  • Your code is properly formatted according to our code style
  • Pull Request title contains the target branch if not targeting main: [0.9.x] Subject
  • Pull Request contains link to the 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
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-quarkus2 to backport the original PR to the quarkus2 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.

@dellamas dellamas requested a review from a team as a code owner June 3, 2025 08:32
@hbelmiro hbelmiro linked an issue Jun 3, 2025 that may be closed by this pull request
Copy link
Contributor

@hbelmiro hbelmiro left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @dellamas.

@hbelmiro hbelmiro merged commit 48f068f into quarkiverse:main Jun 3, 2025
13 checks passed
@hbelmiro
Copy link
Contributor

hbelmiro commented Jun 3, 2025

@all-contributors add @dellamas for tests.

@allcontributors
Copy link
Contributor

@hbelmiro

I've put up a pull request to add @dellamas! 🎉

@hbelmiro
Copy link
Contributor

hbelmiro commented Jun 3, 2025

@dellamas the workflow that automatically cherry-picks PRs to the main-lts branch failed.
Can you please manually cherry-pick this commit to the main-lts branch?

dellamas added a commit to dellamas/quarkus-openapi-generator that referenced this pull request Jun 3, 2025
* Reenable tests on Windows
Issue 868

* Revert "Reenable tests on Windows"

This reverts commit 6393e0c.

* Reenable tests on Windows
Issue 868

* Revert "Reenable tests on Windows"

This reverts commit c780504.

* Reenable tests on Windows
Issue 868

(cherry picked from commit 48f068f)
hbelmiro pushed a commit that referenced this pull request Jun 3, 2025
* Reenable tests on Windows
Issue 868

* Revert "Reenable tests on Windows"

This reverts commit 6393e0c.

* Reenable tests on Windows
Issue 868

* Revert "Reenable tests on Windows"

This reverts commit c780504.

* Reenable tests on Windows
Issue 868

(cherry picked from commit 48f068f)
@dellamas dellamas deleted the issue-868-reenable-tests-on-Windows- branch June 7, 2025 22:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Disable Keycloak Dev Services and reenable tests on Windows

2 participants