You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+4-13Lines changed: 4 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,19 +16,10 @@ reported the issue. Please try to include as much information as you can.
16
16
17
17
## Releases
18
18
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.
21
21
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)
0 commit comments