-
Notifications
You must be signed in to change notification settings - Fork 59
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-641: Remove Job Service All in one image from documentation #642
Conversation
🎊 PR Preview ce2e35c has been successfully built and deployed. See the documentation preview: https://sonataflow-docs-preview-pr-642.surge.sh |
4ba0f6c
to
107be32
Compare
This is not draft anymore, would you mind guys review? |
Hi @kaldesai , this Job Service section is related to the conversation we had in Monday's meeting. |
@gmunozfe please check, this is JS related |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just align the value with the example
serverlessworkflow/modules/ROOT/pages/job-services/core-concepts.adoc
Outdated
Show resolved
Hide resolved
…ts.adoc Co-authored-by: Gonzalo Muñoz <[email protected]>
added |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, good work @wmedvede !
Closes #641
Description:
Please make sure that your PR meets the following requirements:
Issue-XYZ Subject
[0.9.x] Issue-XYZ Subject
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 the7.67.x
branch).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.