We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
For automatic releasing, we should setup release-please GH Action.
We're currently waiting for V4 of release-please (https://github.com/google-github-actions/release-please-action/pull/883) to be released, since we're making use of a develop/main branch.
Steps to take:
Create release-please.yaml with release-please@v4 Should be triggered on push to main. Target branch should be main.
main
This is the current workflow:
gitGraph LR: commit branch "Develop" branch "Feature1" commit checkout "Develop" commit merge "Feature1" branch "Feature2" commit commit checkout "Develop" merge "Feature2" checkout "main" merge "Develop" branch "Release PR" commit id: "Auto generated by Release Please" checkout "main" merge "Release PR" tag: "Release"
Once Release-please is setup correctly and releasing works, we can remove the GH Action release-project.yml and move it into release-please.yml
release-project.yml
release-please.yml
The text was updated successfully, but these errors were encountered:
No branches or pull requests
For automatic releasing, we should setup release-please GH Action.
We're currently waiting for V4 of release-please (https://github.com/google-github-actions/release-please-action/pull/883) to be released, since we're making use of a develop/main branch.
Steps to take:
Create release-please.yaml with release-please@v4
Should be triggered on push to
main
.Target branch should be
main
.This is the current workflow:
Once Release-please is setup correctly and releasing works, we can remove the GH Action
release-project.yml
and move it intorelease-please.yml
The text was updated successfully, but these errors were encountered: