-
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
ResolvedPipelineRunTask
to ResolvedPipelineTask
#5025
Conversation
The following is the coverage report on the affected files.
|
why did the rename decrease the coverage for resultresolution.go? 🤔 |
619039d
to
db07cae
Compare
`ResolvedPipelineRunTask` is a confusing name for a `PipelineTask` and its resources, plus we don't have a `PipelineRunTask` object. This change renames `ResolvedPipelineRunTask` to `ResolvedPipelineTask`. Issue: tektoncd#5024
db07cae
to
646f3b0
Compare
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: 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 |
In tektoncd#5025, we renamed ResolvedPipelineRunTask to ResolvedPipelineTask. In this change, we rename the function that creates it to align with the new type name.
In tektoncd#5025, we renamed ResolvedPipelineRunTask to ResolvedPipelineTask. In this change, we rename the function that creates it to align with the new type name.
In #5025, we renamed ResolvedPipelineRunTask to ResolvedPipelineTask. In this change, we rename the function that creates it to align with the new type name.
Changes
ResolvedPipelineRunTask
is a confusing name for aPipelineTask
and its resources, plus we don't have a
PipelineRunTask
object.This change renames
ResolvedPipelineRunTask
toResolvedPipelineTask
.Issue: #5024
/kind cleanup
cc @pritidesai
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
Release Notes