Skip to content

Commit 33b290d

Browse files
committed
RE: #1421, Add documentation about creating a GitHub release after creating a tag
1 parent b2877f4 commit 33b290d

File tree

1 file changed

+7
-0
lines changed

1 file changed

+7
-0
lines changed

developer_docs/release.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,13 @@ This project release guide is based on
1919
7. `$ git push && git push --tags`
2020
8. `$ git checkout develop`
2121
9. `$ git merge --no-ff release-<newversion>`
22+
10. Create a release on GitHub. You can do this in one of two ways:
23+
1. (Preferred) Use the [`hub` command line tool](https://hub.github.com/). You can automate adding all commit messages since the last release with the following command:
24+
```sh
25+
$ hub release create -d -m "<newversion>" -m "$(git log `git describe --tags --abbrev=0 HEAD^`..HEAD --oneline)" <newversion>`
26+
```
27+
Note that this creates a draft release, which you can then edit on GitHub. This allows you to create release notes from the list of commit messages, but then edit these notes as you wish.
28+
2. [Draft a new release on Github](https://github.com/processing/p5.js-web-editor/releases/new).
2229

2330
Travis CI will automatically deploy the release to production, as well as push a production tagged Docker image to DockerHub.
2431

0 commit comments

Comments
 (0)