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

Auto create PR to upstream OLM repo when a new release is cut #1261

Open
NissesSenap opened this issue Sep 26, 2023 · 3 comments
Open

Auto create PR to upstream OLM repo when a new release is cut #1261

NissesSenap opened this issue Sep 26, 2023 · 3 comments
Labels
enhancement New feature or request help wanted Extra attention is needed triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@NissesSenap
Copy link
Collaborator

Is your feature request related to a problem? Please describe.
As a part of #1234 we won't no longer check in the tag in the bundle/manifests. Instead, we will just set the image digest in the upstream OLM repos.

Since everything is disconnected from each other, we can now automate a PR to the OLM repos when the image has been generated.

Describe the solution you'd like

  • Create a github actions that runs after the container image has been published.
  • clone this repo, update the digest by running the needed command.
  • Create a PR to the OLM repos.
  • Tag the maintainers in the PR and when all checks pass we can perform a merge command.

Describe alternatives you've considered
Keep on doing it manually.

@NissesSenap NissesSenap added enhancement New feature or request needs triage Indicates an issue or PR lacks a `triage/foo` label and requires one. triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Sep 26, 2023
@NissesSenap NissesSenap added the help wanted Extra attention is needed label Sep 26, 2023
@NissesSenap
Copy link
Collaborator Author

To not generate a bunch of PRs to the upstream OLM repos, work on this repo should start in a public repo that the PR creator owns. This way we won't create a bunch of OLM repo PRs.

@NissesSenap
Copy link
Collaborator Author

It's probably a good idea to look at #1313 first.

@NissesSenap
Copy link
Collaborator Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

1 participant