Skip to content

Commit 988f32b

Browse files
author
Joris Conijn
authored
chore: tweak release notes (#36)
1 parent d7da9f8 commit 988f32b

File tree

2 files changed

+19
-6
lines changed

2 files changed

+19
-6
lines changed

.github/workflows/release.yml

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,16 @@ jobs:
2525
run: make install
2626
- name: Run check
2727
run: make build
28+
- name: Create Release
29+
id: create_release
30+
uses: actions/create-release@v1
31+
env:
32+
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
33+
with:
34+
tag_name: ${{ github.ref }}
35+
release_name: Release v${{ steps.vars.outputs.version }}
36+
draft: false
37+
prerelease: false
2838
- name: Upload Release Asset
2939
id: upload-release-asset
3040
uses: actions/upload-release-asset@v1

CONTRIBUTING.md

Lines changed: 9 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -17,18 +17,21 @@ reported the issue. Please try to include as much information as you can.
1717
## Releases
1818

1919
First you will need to update the `version` in the [`pyproject.toml`](./pyproject.toml) file. Next you need to merge the
20-
change to the `main` branch using a pull request.
20+
change to the `develop` branch using a pull request.
21+
22+
Lookup the generated release notes, they are listed as draft. Copy them to a temporary file for later use.
2123

2224
Then you need to create a new release. You can do this by creating a tag and push it to the remote:
2325

24-
```bash
25-
git tag v$(awk '/version/{print $NF}' pyproject.toml | sed 's/\"//g')
26-
git push --tags
27-
```
26+
```bash
27+
git tag v$(awk '/version/{print $NF}' pyproject.toml | sed 's/\"//g')
28+
git push --tags
29+
```
2830

2931
This will trigger the GitHub Actions [`release`](.github/workflows/release.yml) workflow. When the release process is
3032
done. You need to create a pull request from `develop` to `main` and merge it.
3133

32-
Then you need to the releases section on GitHub and publish the new release.
34+
Then you need to the releases section on GitHub and update the new release. Go to the releases section on GitHub and
35+
update the new release with the previously stored release notes.
3336

3437
All done!

0 commit comments

Comments
 (0)