-
Notifications
You must be signed in to change notification settings - Fork 177
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
Adding a new workflow to build a container image tagged main on PR merge #1155
Comments
If a PR is not merged, it will not be included in the dev image. |
If you find PRs are regular, you can also do a nightly or even bi-weekly build instead. That would accomplish the same I think and give you more control of the frequency. |
Hey @qweeah I took a look at the issue. Details
$ oras repo tags ghcr.io/oras-project/oras
v0.12.0
v0.2.0-alpha.1
v0.2.1-alpha.1
v0.13.0
v0.14.0
v0.14.1
v0.15.0
v0.15.1
v0.16.0
v1.0.0-rc.1
v1.0.0-rc.2
v1.0.0
v1.1.0-rc.1
v1.0.1
v1.1.0-rc.2
v1.1.0 If you want to have the latest image tag whenever we create a commit on oras/.github/workflows/release-ghcr.yml Lines 18 to 19 in 01e9cdd
Then the trigger for the new target will be: on:
push:
branches: [main] |
@kranurag7 Thanks for volunteering. |
It would be useful to have a Github workflow that automatically builds a container image whenever a PR is merged into the main branch. In this way, users can play with features from the latest version of the code easily via running a GHCR image without having to build it themselves.
The text was updated successfully, but these errors were encountered: