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

kie-kogito-docs-664: Create a guide for the SonataFlow Operator driven Supporting Services Knative Eventing system configuration #685

Merged
merged 23 commits into from
Nov 9, 2024

Conversation

wmedvede
Copy link
Contributor

@wmedvede wmedvede commented Nov 4, 2024

Closes: #664

Description:

Please make sure that your PR meets the following requirements:

  • You have read the contributions doc
  • Pull Request title is properly formatted: Issue-XYZ Subject
  • Pull Request title contains the target branch if not targeting main: [0.9.x] Issue-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.

@wmedvede wmedvede requested a review from domhanak as a code owner November 4, 2024 09:58
@wmedvede wmedvede requested review from ricardozanini and domhanak and removed request for domhanak November 4, 2024 09:58
…n Supporting Services Knative Eventing system configuration
@wmedvede wmedvede force-pushed the kie-kogito-docs-664 branch from 3ab4e76 to a6c5132 Compare November 4, 2024 10:02
Copy link
Contributor

github-actions bot commented Nov 4, 2024

🎊 PR Preview bdf857c has been successfully built and deployed. See the documentation preview: https://sonataflow-docs-preview-pr-685.surge.sh

@wmedvede
Copy link
Contributor Author

wmedvede commented Nov 4, 2024

Hi @kaldesai , would you mind review this PR?

Copy link
Contributor

@kaldesai kaldesai left a comment

Choose a reason for hiding this comment

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

@wmedvede Just minor suggestions! Otherwise the content LGTM :)

wmedvede and others added 22 commits November 5, 2024 19:08
@wmedvede wmedvede merged commit 9559278 into apache:main Nov 9, 2024
2 checks passed
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.

Create a guide for the SonataFlow Operator driven Supporting Services Knative Eventing system configuration
3 participants