Skip to content

Commit 9ac5091

Browse files
author
Joris Conijn
authored
Merge pull request #38 from Nr18/develop
release: 0.2.1
2 parents d7da9f8 + 3d05601 commit 9ac5091

File tree

2 files changed

+19
-15
lines changed

2 files changed

+19
-15
lines changed

.github/workflows/release.yml

Lines changed: 15 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
name: Create Release
22
on:
33
push:
4-
tags:
5-
- 'v*'
4+
branches:
5+
- main
66

77
jobs:
88
build:
@@ -25,6 +25,19 @@ 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
38+
- uses: release-drafter/release-drafter@v5
39+
env:
40+
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
2841
- name: Upload Release Asset
2942
id: upload-release-asset
3043
uses: actions/upload-release-asset@v1

CONTRIBUTING.md

Lines changed: 4 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -16,19 +16,10 @@ reported the issue. Please try to include as much information as you can.
1616

1717
## Releases
1818

19-
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.
19+
First you will need to update the `version` in the [`pyproject.toml`](./pyproject.toml) file.
20+
Next you need to merge these changes into the `develop` branch using a pull request.
2121

22-
Then you need to create a new release. You can do this by creating a tag and push it to the remote:
23-
24-
```bash
25-
git tag v$(awk '/version/{print $NF}' pyproject.toml | sed 's/\"//g')
26-
git push --tags
27-
```
28-
29-
This will trigger the GitHub Actions [`release`](.github/workflows/release.yml) workflow. When the release process is
30-
done. You need to create a pull request from `develop` to `main` and merge it.
31-
32-
Then you need to the releases section on GitHub and publish the new release.
22+
You need to create a pull request from `develop` to `main` and merge it. This will trigger the GitHub Actions [`release`](.github/workflows/release.yml)
23+
workflow.
3324

3425
All done!

0 commit comments

Comments
 (0)