Merge pull request #3 from shry-project/devel

Deploy test

.github/workflows/shry-deploy-test.yml

@@ -1,22 +1,15 @@
 name: Publish Python distributions to test-PyPI
 on:
   push:
-    tags:
-      - v*
-
-  workflow_dispatch:
-
+    branches: [ "main" ]
+
 jobs:
   deploy-pypi:
     if: github.repository == 'shry-project/SHRY'
 
     runs-on: ubuntu-latest
 
     steps:
-      - name: Exit if not on master branch
-        if: endsWith(github.ref, 'main') == false
-        run: exit -1
-
       - uses: actions/checkout@v3
         with:
             fetch-depth: 0
@@ -33,7 +26,7 @@ jobs:
           python setup.py sdist bdist_wheel
  
       - name: Publish distribution to Test PyPI
-        #if: startsWith(github.ref, 'refs/tags/v')
+        if: startsWith(github.ref, 'refs/tags/v')
         uses: pypa/gh-action-pypi-publish@release/v1
         with:
             user: __token__

README.rst

@@ -172,9 +172,9 @@ Add and push with the new tag
 
     # Push with tag
     git tag <next-version>  # e.g., git tag v1.1.4  # Do not forget "v" before the version number!
-    git push origin devel --tags  # or to the new branch
+    git push origin devel --tags  # or to the new branch # Do not push to the mater branch!!
 
-Merge the devel branch to the master branch. The implemented GitHub Action checks if the automatic deploy works using test-pyPI (only if the commit is tagged correctly, e.g., v1.1.0 or v1.1.0-alpha).
+Make a pull request for merging the devel branch to the master branch by hand. The implemented GitHub Action checks if the automatic deploy works using test-pyPI (only if the commit is tagged correctly, e.g., v1.1.0 or v1.1.0-alpha).
 
 Finally, do a new release with a release note on GitHub. The new release triggers an implemented GitHub Action that automatically uploads the package to PyPI (if the commit is tagged correctly, e.g., v1.1.0 or v1.1.0-alpha).