Skip to content

Commit 0723dd3

Browse files
authored
Update README.md
1 parent ac46222 commit 0723dd3

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

README.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -47,11 +47,11 @@ To run the actual **electron app**:
4747

4848
The release process is automated. Follow the steps below.
4949

50-
1. Create a [new **draft** release](https://github.com/manosim/gitify/releases/new). Set the tag version to something with the format of `v1.2.3`. Save as a **draft**.
51-
2. Once everything is merged to `master`, create a branch that starts with `release/vX.X.X` (ie. `release/v1.2.3`).
52-
3. In the same branch, **bump the version** of the app in the `package.json` file and open a PR. GitHub Actions will build, sign and upload the release assets for each commit to that branch as long as a branch is named like `release/vX.X.X` and there is a draft release with the same version number(`package.json`).
53-
4. Merge your release branch into `master`.
54-
5. Publish the draft release once you've added notes to it and all assets are there.
50+
1. Create a [new **draft** release](https://github.com/manosim/gitify/releases/new). Set the tag version to something with the format of `v1.2.3`. Save as a **draft**.
51+
2. Once everything is merged to `master`, create a branch that starts with `release/vX.X.X` (ie. `release/v1.2.3`).
52+
3. In the same branch, **bump the version** of the app in the `package.json` file and open a PR. GitHub Actions will build, sign and upload the release assets for each commit to that branch as long as a branch is named like `release/vX.X.X` and there is a draft release with the same version number(`package.json`).
53+
4. Merge your release branch into `master`.
54+
5. Publish the draft release once you've added notes to it and all assets are there.
5555

5656
### Tests
5757

0 commit comments

Comments
 (0)