From 33b290dc9e665148978909959f6161cfbedec526 Mon Sep 17 00:00:00 2001 From: Cassie Tarakajian Date: Mon, 1 Jun 2020 15:31:59 -0400 Subject: [PATCH] RE: #1421, Add documentation about creating a GitHub release after creating a tag --- developer_docs/release.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/developer_docs/release.md b/developer_docs/release.md index 87ced793..302c8019 100644 --- a/developer_docs/release.md +++ b/developer_docs/release.md @@ -19,6 +19,13 @@ This project release guide is based on 7. `$ git push && git push --tags` 8. `$ git checkout develop` 9. `$ git merge --no-ff release-` +10. Create a release on GitHub. You can do this in one of two ways: + 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: + ```sh + $ hub release create -d -m "" -m "$(git log `git describe --tags --abbrev=0 HEAD^`..HEAD --oneline)" ` + ``` + 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. + 2. [Draft a new release on Github](https://github.com/processing/p5.js-web-editor/releases/new). Travis CI will automatically deploy the release to production, as well as push a production tagged Docker image to DockerHub.