-
Notifications
You must be signed in to change notification settings - Fork 17
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
Automate developer processes #110
Comments
Submitted babylonlabs-io/.github#18 for the template of goreleaser / changelog reminer templates. Will apply them to babylon repositories after being merged. Regarding auto backport, the link suggests to use mergify, which seems to require some setup, including the credentials, accounts in mergify websites, etc.. This is a bit heavy to me and adds one more CI pipeline (apart from GH action). What do you guys think about using some Github actions for auto backport, e.g., https://github.com/marketplace/actions/backporting? |
PR for backport GH action #149 |
Part of #110 This PR introduces the backport Github action. One can label a hotfix PR to `main` with `backport release/0.Y.x`, and this GH action will open a backport PR automatically.
Resolves #110 This PR adds Github actions for changelog reminder and goreleaser. Also this PR bumps the dependency of babylonlabs-io/.github to v0.7.0 TODOs before merging: - [x] wait until v0.7.0 tag of https://github.com/babylonlabs-io/.github - [x] apply v0.7.0 to all reusable workflows
Currently a lot processes in Babaylon node repo is manual and error prone (easy to forget about).
This ticket proposes to automate:
The text was updated successfully, but these errors were encountered: