This repository was archived by the owner on Jun 16, 2025. It is now read-only.
Add release please action #71
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Automate the release creation for db-rocket. This ensures that
The mechanism: PR's should be merged via a specific format of the commit message, which instructs the release-please action how to increase the version. Then a release can be triggered by merging the PR opened by the release-please action. To help users with having the right format for the commit message, we should set the default commit message for merging PR to be the title and ensure during the review that the title is in the correct format. The correct format is:
Added tests?
Added to documentation?