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

CI: Fix set operator_version attribute #415

Merged
merged 1 commit into from
Jul 21, 2023

Conversation

radtriste
Copy link
Contributor

JIRA:

Description:

Please make sure that your PR meets the following requirements:

  • You have read the contributions doc
  • 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
  • The nav.adoc file has a link to this guide in the proper category
  • The index.adoc file has a card to this guide in the proper category, with a meaningful description
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.

@netlify
Copy link

netlify bot commented Jul 21, 2023

Deploy Preview for tangerine-crostata-04a6bf ready!

Name Link
🔨 Latest commit a287179
🔍 Latest deploy log https://app.netlify.com/sites/tangerine-crostata-04a6bf/deploys/64ba976dcf65360008c08605
😎 Deploy Preview https://deploy-preview-415--tangerine-crostata-04a6bf.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@ricardozanini ricardozanini merged commit 104eb80 into apache:main Jul 21, 2023
github-actions bot pushed a commit that referenced this pull request Jul 21, 2023
github-actions bot pushed a commit that referenced this pull request Jul 21, 2023
github-actions bot pushed a commit that referenced this pull request Jul 21, 2023
@radtriste radtriste deleted the fix_set_operator_version_attr branch July 21, 2023 18:11
radtriste added a commit that referenced this pull request Jul 21, 2023
* CI: Fix set `operator_version` attribute (#415)

* Update antora.yml

---------

Co-authored-by: Tristan Radisson <[email protected]>
radtriste added a commit that referenced this pull request Jul 21, 2023
* CI: Fix set `operator_version` attribute (#415)

* Update antora.yml

---------

Co-authored-by: Tristan Radisson <[email protected]>
radtriste added a commit that referenced this pull request Jul 21, 2023
* CI: Fix set `operator_version` attribute (#415)

* Update antora.yml

---------

Co-authored-by: Tristan Radisson <[email protected]>
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.

3 participants