-
Notifications
You must be signed in to change notification settings - Fork 638
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
Add note for revision vs commitID [ci skip] #3540
Conversation
Per FD#2725, added a note explaining the difference in behavior between passing a git tag or branch name vs. passing a commit ID using -r. [ci skip] Signed-off-by: Llewellyn vd Berg <[email protected]>
docs/metadata.rst
Outdated
@@ -62,6 +62,8 @@ manifest Entries of the workflow manifest. | |||
| Properties marked with a `*` are accessible only in the workflow completion and error handlers. See the `Completion handler`_ section for details. | |||
| | |||
|
|||
.. note:: | |||
When passing a git tag or branch name using the ``-r`` argument in your CLI command, the ``workflow.revision`` and the associated ``workflow.commitId`` is populated. When passing only the Git commit ID using ``-r``, no ``workflow.revision`` is returned. |
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.
When passing a git tag or branch name using the ``-r`` argument in your CLI command, the ``workflow.revision`` and the associated ``workflow.commitId`` is populated. When passing only the Git commit ID using ``-r``, no ``workflow.revision`` is returned. | |
When passing a Git tag or branch name using the ``-r`` argument in your CLI command, the ``workflow.revision`` and the associated ``workflow.commitId`` is populated. When passing only the Git commit ID using ``-r``, no ``workflow.revision`` is returned. |
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.
Should not be "are populated" ?
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.
Certainly. Thanks for catching.
Signed-off-by: Llewellyn vd Berg <[email protected]>
Signed-off-by: Llewellyn vd Berg <[email protected]>
Signed-off-by: Llewellyn vd Berg <[email protected]> Signed-off-by: Marco De La Pierre <[email protected]>
Signed-off-by: Llewellyn vd Berg <[email protected]>
Per FD#2725, added a note explaining the difference in behavior between passing a git tag or branch name vs. passing a commit ID using the
-r
argument.Signed-off-by: Llewellyn vd Berg [email protected]