-
Notifications
You must be signed in to change notification settings - Fork 47
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
Update the Workflow to do a dev-release #278
Comments
Hi @bupd, I'm a bit confused about the conditions for triggering push-latest-images and publish-release. Does it only trigger when the pushed branch is main or when a Git tag is pushed, to generate and publish new images? To put it simply, does this mean that the GitHub Actions for push-latest-images and publish-release will only be triggered when a branch is merged into main, or when a new version of harbor-cli is released? |
To simply put it. There will be two releases. |
Reopening this issue, Since the dev-release of Harbor-Cli is still not made. |
Inqould suggest using the latest tag instead and fthe "dev" tag |
Change the
push-latest-images
andpublish-release
conditions to the below given condition.With the above change we should have a Release for every push to
main
branch.The text was updated successfully, but these errors were encountered: