-
Notifications
You must be signed in to change notification settings - Fork 19
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
implement workflows for automatic releases #22
Conversation
Signed-off-by: Lukas Hauser <lukas.hauser@tngtech.com>
Signed-off-by: Lukas Hauser <lukas.hauser@tngtech.com>
To trigger this workflow automatically, we could consider adding What do you think about this PR @chlins @wy65701436 @Vad1mo ? |
Thank you for your contribution, this looks good. |
Hi, @luka5 After I merged your PR and triggered the action "Prepare new release" and input 2.10.0. but there is no release named 2.10.0 created. could you please describe the detail process to create a new release? |
Hi @stonezdj, the "Prepare new release" run (https://github.com/goharbor/go-client/actions/runs/7499663802/job/20416866914) did create #23. Now you can review it and approve. After merge, the new release will be created in https://github.com/goharbor/go-client/actions/workflows/tag-release.yml |
@luka5 can we add that feature |
here we go: #24 |
As discussed in #19, I did implement some workflows to automate the release process. This process now looks like:
make gen-harbor-api
This requires the setting
Allow GitHub Actions to create and approve pull requests
inSettings > Actions > General
to be enabled.Tested in https://github.com/luka5/go-client/pulls