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

Improving documentation around new image tags, cleanup old Operator-SDK logic #247

Merged
merged 3 commits into from
Nov 11, 2022

Conversation

mjlshen
Copy link
Contributor

@mjlshen mjlshen commented Nov 11, 2022

OSD-13437: Continuing cleanup work as a result of #246 before releasing a v3.0.1

  • Tidying up the README a bit and adding a callout that we need a team lead to help push tags
  • Cleaning up some logic around old operator-sdk versions in the golang-osd-operator convention
  • Sharing the ALLOW_DIRTY_CHECKOUT workaround in the error message of make isclean
  • Updating fips logic as now we just need to set an environment variable GOEXPERIMENT=boringcrypto all: move dev.boringcrypto into main branch behind GOEXPERIMENT golang/go#51940 (comment)

Copy link
Member

@2uasimojo 2uasimojo left a comment

Choose a reason for hiding this comment

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

This looks great. One small suggestion inline

MAINPACKAGE = ./cmd/manager
API_DIR = ./pkg/apis
endif
API_DIR = ./api
Copy link
Member

Choose a reason for hiding this comment

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

Or just inline it. Is it used anywhere else?

Copy link
Member

Choose a reason for hiding this comment

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

All three of these, actually.

Unless they're overridden in consuming projects?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

They shouldn't be overridden since we should all have the same structure, so +1

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 11, 2022

@mjlshen: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Copy link
Member

@2uasimojo 2uasimojo left a comment

Choose a reason for hiding this comment

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

/lgtm

thanks!

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 11, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 11, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 2uasimojo, mjlshen

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 Nov 11, 2022
@openshift-merge-robot openshift-merge-robot merged commit 71af0af into openshift:master Nov 11, 2022
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. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants