Skip to content

Commit

Permalink
fix: Update README with correct release procedure (#247)
Browse files Browse the repository at this point in the history
Signed-off-by: Fernando Diaz <[email protected]>
  • Loading branch information
fediazgon authored Nov 25, 2021
1 parent 3cafd38 commit e920b08
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 4 deletions.
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

0 comments on commit e920b08

Please sign in to comment.