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

Re-run make generate and generate-crds #786

Merged
merged 1 commit into from
Jun 9, 2021

Conversation

imjasonh
Copy link
Contributor

Changes

It seems like the repo has gotten out of sync with generated code, which led to some unnecessary diffs in some changes I was working on. Mostly just copyright headers and diffs from controller-gen v0.4.1 -> v0.5.0.

Should we have a CI check that tries to check that codegen is up-to-date?

Also git-ignore binaries generated by go build ./cmd/....

/kind cleanup

Submitter Checklist

  • [n/a] Includes tests if functionality changed/was added
  • [n/a] Includes docs if changes are user-facing
  • [y] Set a kind label on this PR
  • [y] Release notes block has been filled in, or marked NONE

See the contributor guide
for details on coding conventions, github and prow interactions, and the code review process.

Release Notes

NONE

@imjasonh imjasonh requested a review from qu1queee May 26, 2021 13:53
@openshift-ci openshift-ci bot added kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. release-note-none Label for when a PR does not need a release note labels May 26, 2021
@openshift-ci openshift-ci bot requested a review from gabemontero May 26, 2021 13:53
@qu1queee
Copy link
Contributor

@imjasonh btw, I think CI is not calling our make generate-crds target

@adambkaplan
Copy link
Member

Should we have a CI check that tries to check that codegen is up-to-date?

Yes - our go code needs to be the source of truth. Any PR that changes our API godoc needs to ensure that the generated CRDs include those changes, otherwise we'll never update our API on the cluster.

Copy link
Contributor

@qu1queee qu1queee left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Merging as this is currently blocking our v0.5.0, we will take the concerns on crds with new lines or not offline.

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 9, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 9, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: qu1queee

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 9, 2021
@openshift-merge-robot openshift-merge-robot merged commit a1e7d1a into shipwright-io:main Jun 9, 2021
@sbose78
Copy link
Member

sbose78 commented Jun 10, 2021

Good catch!

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/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lgtm Indicates that a PR is ready to be merged. release-note-none Label for when a PR does not need a release note
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants