@@ -39,7 +39,7 @@ on your workstation as follows::
3939
4040In both cases tox -p runs in parallel the following checks:
4141
42- - Build Spinx Documentation
42+ - Build Sphinx Documentation
4343 - run pytest on all tests in ./tests
4444 - run mypy linting on all files in ./src ./tests
4545 - run pre-commit checks:
@@ -126,10 +126,14 @@ Release Process
126126To make a new release, please follow this checklist:
127127
128128- Choose a new PEP440 compliant release number
129- - Git tag the version
130- - Push to GitHub and the actions will make a release on pypi
131- - Push to internal gitlab and do a dls-release.py of the tag
132- - Check and edit for clarity the autogenerated GitHub release _
129+ - Go to the GitHub release _ page
130+ - Choose ``Draft New Release ``
131+ - Click ``Choose Tag `` and supply the new tag you chose (click create new tag)
132+ - Click ``Generate release notes ``, review and edit these notes
133+ - Choose a title and click ``Publish Release ``
134+
135+ Note that tagging and pushing to the main branch has the same effect except that
136+ you will not get the option to edit the release notes.
133137
134138.. _release : https://github.com/epics-containers/python3-pip-skeleton/releases
135139
@@ -149,7 +153,7 @@ Python project structure which provides a means to keep tools and
149153techniques in sync between multiple Python projects. To update to the
150154latest version of the skeleton, run::
151155
152- $ git pull https://github.com/dls-controls/python3-pip-skeleton skeleton
156+ $ git pull https://github.com/dls-controls/python3-pip-skeleton main
153157
154158Any merge conflicts will indicate an area where something has changed that
155159conflicts with the setup of the current module. Check the `closed pull requests
0 commit comments