-
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
Add the git resource ref to the ResourceResult for git resources. #2238
Conversation
Could you add a bit of explanation around the intended purpose? Is it related to a specific bug or feature request? |
a04f24b
to
715280b
Compare
This includes the full name of the git resource in the resource result for git resources. We pass this along in the environment variable already, this includes it back in the resource result so we can tie the commit sha and branch name in the result. Right now Task results contain the exact commit that was cloned from any git resource inputs, but the "resourceref" field is empty. That makes it hard to tell which repo was cloned after. In the case of multiple inputs, there is no way to tell which result corresponds to which.
Added some more to the commit message. I think this was something just overlooked, so halfway between a feature request and a bug. |
/test pull-tekton-pipeline-integration-tests |
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: dibyom, vdemeester 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 |
Changes
This includes the full name of the git resource in the resource result for
git resources. We pass this along in the environment variable already, this
includes it back in the resource result so we can tie the commit sha and
branch name in the result.
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
See the contribution guide for more details.
Double check this list of stuff that's easy to miss:
cmd
dir, please updatethe release Task to build and release this image.
Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.
Release Notes