Each commit in the pull request is processed individually as a
single commit before submitting to Gerrit repository. This option
allows you to preserve git history. This requires inputs.SUBMIT_SINGLE_COMMITS to be set to 'true'
from the caller.
Remove extra inputs. Gerrit server and port and the project must be read
from .gitreview file. Composite actions are limited on
the number of inputs that can be passed to 10.
Support USE_PR_AS_COMMIT flag, allows commit message to be
replaced the pull request body and title.
Note: the 50/72 rule of the title and body needs to be taken
care of by the developer or the pre-commit verification would fail.
Comment the PR URL link along with the workflow run URL on the
Gerrit change request using ssh gerrit review CLI. This is
useful to Jenkins jobs to query comments on the change and search
for PR-### URL therefore allow developer comments to be sync back
to the pull request on Github.
Prefix the git-review topic with the project name followed by
PR-### to ensure the same topic is not overused from different projects
under the same organization.
Update docs and examples caller workflows accordingly.
Each commit in the pull request is processed individually as a single commit before submitting to Gerrit repository. This option allows you to preserve git history. This requires
inputs.SUBMIT_SINGLE_COMMITSto be set to 'true' from the caller.Remove extra inputs. Gerrit server and port and the project must be read from .gitreview file. Composite actions are limited on the number of inputs that can be passed to 10.
Support USE_PR_AS_COMMIT flag, allows commit message to be replaced the pull request body and title. Note: the 50/72 rule of the title and body needs to be taken care of by the developer or the pre-commit verification would fail.
Comment the PR URL link along with the workflow run URL on the Gerrit change request using
ssh gerrit reviewCLI. This is useful to Jenkins jobs to query comments on the change and search for PR-### URL therefore allow developer comments to be sync back to the pull request on Github.Prefix the git-review topic with the project name followed by PR-### to ensure the same topic is not overused from different projects under the same organization.
Update docs and examples caller workflows accordingly.