Skip to content
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

pkg/apis: remove duplicate MergeStepsWithStepTemplate function #3572

Merged
merged 1 commit into from Dec 1, 2020

Conversation

vdemeester
Copy link
Member

Changes

Remove duplicated function MergeStepsWithStepTemplate.

/kind misc

/cc @tektoncd/core-maintainers

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

  • Includes tests (if functionality changed/added)
  • Includes docs (if user facing)
  • Commit messages follow commit message best practices
  • Release notes block has been filled in or deleted (only if no user facing changes)

See the contribution guide for more details.

Double check this list of stuff that's easy to miss:

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

NONE

Signed-off-by: Vincent Demeester <vdemeest@redhat.com>
@tekton-robot tekton-robot requested a review from a team December 1, 2020 11:02
@tekton-robot tekton-robot added release-note-none Denotes a PR that doesnt merit a release note. kind/misc Categorizes issue or PR as a miscellaneuous one. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Dec 1, 2020
@vdemeester vdemeester requested review from afrittoli, pritidesai and a user December 1, 2020 11:02
@vdemeester
Copy link
Member Author

/retest

@dlorenc
Copy link
Contributor

dlorenc commented Dec 1, 2020

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Dec 1, 2020
@ghost
Copy link

ghost commented Dec 1, 2020

Looks ok to me but just wanna check - is there a specific motivation for this change? I thought a lot of the code in the v1alpha1 package was intentionally duplicated / aliased?

@vdemeester
Copy link
Member Author

Looks ok to me but just wanna check - is there a specific motivation for this change? I thought a lot of the code in the v1alpha1 package was intentionally duplicated / aliased?

No real motivation except I was looking at some code and this dead code / duplicated code bothered me. Some duplicated code was initially "intentional" when we were storing v1alpha1 object. Now it is less "intentional" and more "it's v1alpha1 so it is less important to modify".

@tekton-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sbwsg

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 1, 2020
@tekton-robot tekton-robot merged commit ba2d2e7 into tektoncd:master Dec 1, 2020
@vdemeester vdemeester deleted the apis-remove-dup-merge branch December 1, 2020 16:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/misc Categorizes issue or PR as a miscellaneuous one. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesnt merit a release note. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants