Skip to content
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

fix: Update README with correct release procedure #247

Merged
merged 1 commit into from
Nov 25, 2021
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 1 addition & 2 deletions README.rst
Original file line number Diff line number Diff line change
Expand Up @@ -222,5 +222,4 @@ URL of your target FlyteAdmin API instance. These instructions will use
=======
Release
=======
To release, you have to annotate the PR message to include either #minor,
#patch or #major.
To release, you have to annotate the PR message to include one of the following `commit-analyzer types <https://github.com/semantic-release/commit-analyzer#rules-matching>`_.
5 changes: 3 additions & 2 deletions pull_request_template.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,8 +2,9 @@

_- Make sure to use a concise title for the pull-request._

_- Use #patch, #minor or #major in the pull-request title to bump the corresponding version. Otherwise, the patch version
will be bumped. [More details](https://github.com/marketplace/actions/github-tag-bump)_
_- if you want to create a new release, make sure to modify your commit message to include one
of [commit-analyzer types](https://github.com/semantic-release/commit-analyzer#rules-matching).
More information in [semantic-release.gitbook.io](https://semantic-release.gitbook.io/semantic-release/#commit-message-format)._

# TL;DR
_Please replace this text with a description of what this PR accomplishes._
Expand Down