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

Add release header to the .goreleaser configuration file #2760

Conversation

timflannagan
Copy link
Contributor

Description of the change:
Add release header to the .goreleaser configuration file.

Motivation for the change:
Closes #2559

Reviewer Checklist

  • Implementation matches the proposed design, or proposal is updated to match implementation
  • Sufficient unit test coverage
  • Sufficient end-to-end test coverage
  • Docs updated or added to /doc
  • Commit messages sensible and descriptive
  • Tests marked as [FLAKE] are truly flaky
  • Tests that remove the [FLAKE] tag are no longer flaky

@openshift-ci
Copy link

openshift-ci bot commented Apr 28, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: timflannagan

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 Apr 28, 2022
@timflannagan timflannagan force-pushed the release/add-release-install-header branch from e43e3fa to 27f8e6d Compare April 28, 2022 21:35
@timflannagan
Copy link
Contributor Author

/cc @awgreene @exdx

@openshift-ci openshift-ci bot requested review from awgreene and exdx April 28, 2022 21:35
@timflannagan timflannagan force-pushed the release/add-release-install-header branch from 27f8e6d to a2c2ec3 Compare April 28, 2022 21:43
@perdasilva
Copy link
Collaborator

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 29, 2022
@timflannagan timflannagan force-pushed the release/add-release-install-header branch from a2c2ec3 to 9e438ee Compare April 29, 2022 13:05
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Apr 29, 2022
@perdasilva
Copy link
Collaborator

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 29, 2022
Signed-off-by: timflannagan <timflannagan@gmail.com>
@timflannagan timflannagan force-pushed the release/add-release-install-header branch from 9e438ee to 92d01e4 Compare April 29, 2022 14:13
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Apr 29, 2022
@openshift-ci
Copy link

openshift-ci bot commented Apr 29, 2022

New changes are detected. LGTM label has been removed.

@timflannagan timflannagan added the lgtm Indicates that a PR is ready to be merged. label Apr 29, 2022
@openshift-merge-robot openshift-merge-robot merged commit acc4c5a into operator-framework:master Apr 29, 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.

GORELEASER should generate install directions for each release.
3 participants