-
Notifications
You must be signed in to change notification settings - Fork 57
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
KOGITO-8410 Added documentation about GET requests to Knative Custom Functions #451
Conversation
…Functions. Signed-off-by: Helber Belmiro <[email protected]>
✅ Deploy Preview for tangerine-crostata-04a6bf ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Maybe adding a note saying that the arguments are sent over query string? I know that's obvious, but.... |
Signed-off-by: Helber Belmiro <[email protected]>
Done. |
serverlessworkflow/modules/ROOT/pages/core/custom-functions-support.adoc
Outdated
Show resolved
Hide resolved
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.
@hbelmiro Your changes look good to me. Thank you.
…pport.adoc Co-authored-by: Kalyani Desai <[email protected]>
@radtriste we should've waited for https://github.com/kiegroup/kogito-runtimes/pull/3172 But I guess we haven't branched? If so, that PR must be cherry-picked. |
sorry I saw it after ... |
JIRA: https://issues.redhat.com/browse/KOGITO-8410
This PR depends on:
Please make sure that your PR meets the following requirements:
KOGITO-XYZ Subject
[0.9.x] KOGITO-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.