-
Notifications
You must be signed in to change notification settings - Fork 6
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 all the valid semantic version tags #24
Add all the valid semantic version tags #24
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mkumatag The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@@ -3,7 +3,7 @@ name: Build and Publish RSCT Operator | |||
on: | |||
push: | |||
tags: | |||
- '[0-9]+.[0-9]+.[0-9]+' | |||
- 'v*.*.*' |
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.
The Operator SDK does not support the 'v' character in version numbers; therefore, used versions without 'v'. To address this, we can modify -
run: echo "VERSION=$(echo ${GITHUB_REF/refs\/tags\//})" >> $GITHUB_ENV |
echo "VERSION=$(echo ${GITHUB_REF/refs\/tags\/v/})" >> $GITHUB_ENV
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.
okay, lemme do that then..
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.
done that change, ptal to the latest codechange
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.
/lgtm
Signed-off-by: Manjunath Kumatagi <[email protected]>
0812415
into
ocp-power-automation:main
Here is the valid description for the tags per the GitHub release process
Tagging suggestions
The current code doesn't deal with the above scenario, hence this PR will address this issue.