-
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
[TEP-0133] Apply default resolver to finally tasks #6481
[TEP-0133] Apply default resolver to finally tasks #6481
Conversation
Fixes tektoncd#6449. Prior to this commit, the default resolver is only applied to PipelineTasks but not finally PipelineTasks. This commit applies the default resolver to the finally PipelineTasks in the same way as normal PipelineTasks. This commit also refactors the common code to a PipelineTask SetDefaults function. /kind bug [tektoncd#6449]: tektoncd#6449
Skipping CI for Draft Pull Request. |
/test all |
/assign @chitrangpatel |
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: lbernick 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
Fixes #6449. Prior to this commit, the default resolver is only applied to PipelineTasks but not finally PipelineTasks.
This commit applies the default resolver to the finally PipelineTasks in the same way as normal PipelineTasks. This commit also refactors the common code to a PipelineTask SetDefaults function.
/kind bug
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