Fixed git command.

dev
Franco Masotti 2 years ago
parent 0c9790cee1
commit 91e3e03f25
Signed by: frnmst
GPG Key ID: 24116ED85666780A
  1. 8
      _posts/2018-04-16-my-python-release-workflow.md

@ -1,7 +1,7 @@
---
title: My Python release workflow
tags: [python, git, workflow, aur, arch]
updated: 2020-05-21 17:53
updated: 2020-06-23 15:55
description: A personal reminder with the instructions for releasing new versions of Python packages
---
@ -40,7 +40,7 @@ in case of a new version release with some of my Python repositories.
1. `ln -s ${project_name}_asciinema_${MAJOR}_${OLD_MINOR}_${OLD_PATCH}_demo.sh ${project_name}_asciinema_${MAJOR}_${MINOR}_${PATCH}_demo.sh`
2. `ln -s ${project_name}_asciinema_${MAJOR}_${OLD_MINOR}_${OLD_PATCH}.json ${project_name}_asciinema_${MAJOR}_${MINOR}_${PATCH}.json`
2. `git add -A`
3. `git commit -am "${commit_message}"`
3. `git commit -m "${commit_message}"`
4. `git push`
4. if necessary, update version numbers, requirements
@ -64,7 +64,7 @@ in case of a new version release with some of my Python repositories.
- all Python source files
- all downstream distribution packages (see the `./packages` directory)
12. `git add -A`
13. `git commit -am "Preparing for new release."`
13. `git commit -m "Preparing for new release."`
14. `git push`
5. update the documentation
@ -74,7 +74,7 @@ in case of a new version release with some of my Python repositories.
4. `rm -rf _sources _static`
5. `mv ~/html/{*,.nojekyll,.buildinfo} .`
6. `git add -A`
7. `git commit -am "New release."`
7. `git commit -m "New release."`
8. `git push`
6. merge the `${dev_branch}` branch into `master` and create a new annotated git tag

Loading…
Cancel
Save