remove release to PiPy

.gitea/workflows/release.yml

@@ -30,23 +30,23 @@ jobs:
         with:
           body_path: release_message.md
 
-  deploy:
-    needs: release
-    runs-on: ubuntu-latest
-    steps:
-    - uses: actions/checkout@v3
-    - name: Set up Python
-      uses: actions/setup-python@v4
-      with:
-        python-version: '3.x'
-    - name: Install dependencies
-      run: |
-        python -m pip install --upgrade pip
-        pip install setuptools wheel twine
-    - name: Build and publish
-      env:
-        TWINE_USERNAME: __token__
-        TWINE_PASSWORD: ${{ secrets.PYPI_API_TOKEN }}
-      run: |
-        python setup.py sdist bdist_wheel
-        twine upload dist/*
+  # deploy:
+  #   needs: release
+  #   runs-on: ubuntu-latest
+  #   steps:
+  #   - uses: actions/checkout@v3
+  #   - name: Set up Python
+  #     uses: actions/setup-python@v4
+  #     with:
+  #       python-version: '3.x'
+  #   - name: Install dependencies
+  #     run: |
+  #       python -m pip install --upgrade pip
+  #       pip install setuptools wheel twine
+  #   - name: Build and publish
+  #     env:
+  #       TWINE_USERNAME: __token__
+  #       TWINE_PASSWORD: ${{ secrets.PYPI_API_TOKEN }}
+  #     run: |
+  #       python setup.py sdist bdist_wheel
+  #       twine upload dist/*

ABOUT_THIS_TEMPLATE.md

@@ -112,7 +112,7 @@ with module imports or anything else, it is useful for CI, logs and debugging.
 ### Why to include `tests`, `history` and `Containerfile` as part of the release?
 
 The `MANIFEST.in` file is used to include the files in the release, once the 
-project is released to PyPI all the files listed on MANIFEST.in will be included
+project is released to artifactory all the files listed on MANIFEST.in will be included
 even if the files are static or not related to Python.
 
 Some build systems such as RPM, DEB, AUR for some Linux distributions, and also

CONTRIBUTING.md

@@ -95,10 +95,7 @@ init:             ## Initialize the project based on an application template.
 
 This project uses [semantic versioning](https://semver.org/) and tags releases with `X.Y.Z`
 Every time a new tag is created and pushed to the remote repo, gitea actions will
-automatically create a new release on gitea and trigger a release on PyPI.
-
-For this to work you need to setup a secret called `PIPY_API_TOKEN` on the project settings>secrets, 
-this token can be generated on [pypi.org](https://pypi.org/account/).
+automatically create a new release on gitea.
 
 To trigger a new release all you need to do is.
 

README.md

@@ -11,10 +11,8 @@ See also
 1. Create a new repository from this template and choose a name for your project
    (e.g. `my_awesome_project` - recommendation is to use all lowercase and underscores separation for repo names.)
 2. Wait until the first run of CI finishes (Gitea Actions will process the template and commit to your new repo)
-3. If you want Automatic Release to [PyPI](https://pypi.org)  
-  On the new repository `settings->secrets` add your `PYPI_API_TOKEN` (get the tokens on PyPI website)
-4. Read the file [CONTRIBUTING.md](CONTRIBUTING.md)
-5. Then clone your new project and happy coding!
+3. Read the file [CONTRIBUTING.md](CONTRIBUTING.md)
+4. Then clone your new project and happy coding!
 
 > **NOTE**: **WAIT** until first CI run on gitea actions before cloning your new project.
 
@@ -31,7 +29,6 @@ See also
   `Containerfile` is a more open standard for building container images than Dockerfile, you can use buildah or docker with this file.
 - 🧪 Testing structure using [pytest](https://docs.pytest.org/en/latest/)
 - ✅ Code linting using [flake8](https://flake8.pycqa.org/en/latest/)
-- 🛳️ Automatic release to [PyPI](https://pypi.org) using [twine](https://twine.readthedocs.io/en/latest/) and gitea actions.
 - 🎯 Entry points to execute your program using `python -m <project_name>` or `$ project_name` with basic CLI argument parsing.
 - 🔄 Continuous integration using [Gitea Actions](.gitea/workflows/) with jobs to lint, test and release your project on Linux, Mac and Windows environments.
 
@@ -44,12 +41,6 @@ See also
 
 project_description
 
-## Install it from PyPI
-
-```bash
-pip install project_name
-```
-
 ## Usage
 
 ```py