-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
tekton: do not fail on git status -s
#5587
tekton: do not fail on git status -s
#5587
Conversation
It turns out, `git status -s` fails if the working directory is a "detached" head, which is what happens in our case. This removes that checks as it renders `pipeline` not releasable at all. It also "locally" tag it to the specified version so that it will appear in the go build metadata. Signed-off-by: Vincent Demeester <[email protected]>
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
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: abayer 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 |
/cherrypick release-v0.40.x (Just in case we have to do a 0.40.3 🙃 ) |
@vdemeester: new pull request created: #5590 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Changes
It turns out,
git status -s
fails if the working directory is a "detached" head, which is what happens in our case. This removes that checks as it renderspipeline
not releasable at all.It also "locally" tag it to the specified version so that it will appear in the go build metadata.
Signed-off-by: Vincent Demeester [email protected]
/kind misc
/cc @afrittoli @abayer @imjasonh
Note: I used this to release 0.40.2 already 🙃
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
functionality, content, code)
/kind <type>
. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tepRelease Notes