templatepy 0.2.3__tar.gz → 0.2.6__tar.gz

{templatepy-0.2.3 → templatepy-0.2.6}/.bumpversion.cfg

@@ -1,5 +1,5 @@
 [bumpversion]
-current_version = 0.2.3
+current_version = 0.2.6
 commit = True
 tag = False
 tag_name = v{new_version}

{templatepy-0.2.3 → templatepy-0.2.6}/PKG-INFO

@@ -1,7 +1,7 @@
 Metadata-Version: 2.1
 Name: templatepy
-Version: 0.2.3
-Summary: templatepy: template for derivative python packages
+Version: 0.2.6
+Summary: templatepy: Template repo for python repositories & PyPi integration
 Author-email: "Lars B. Rollik" <L.B.Rollik@protonmail.com>
 License: BSD 3-Clause License
         
@@ -38,6 +38,7 @@ Project-URL: Issue Tracker, https://github.com/larsrollik/templatepy/issues
 Classifier: Intended Audience :: Developers
 Classifier: Topic :: Software Development :: Libraries :: Python Modules
 Classifier: License :: OSI Approved :: BSD License
+Classifier: Operating System :: OS Independent
 Classifier: Programming Language :: Python
 Classifier: Programming Language :: Python :: 3
 Classifier: Programming Language :: Python :: 3.10
@@ -91,7 +92,7 @@ Requires-Dist: toml; extra == "dev"
 # templatepy
 Template repo for python repositories & PyPi integration
 ---
-**Version: "0.2.3"**
+**Version: "0.2.6"**
 
 
 ## Usage
@@ -264,7 +265,6 @@ The package will then be automatically uploaded to [PyPI](https://pypi.org/) or
 
 ## Github Flow overview
 
-
 1) Create a new feature branch from main using git checkout -b.
 2) Make and commit a dummy change (e.g., adding a file).
 3) Use bumpversion to bump the version (you can adjust patch, minor, or major based on what change you want), and create a release tag.
@@ -272,6 +272,7 @@ The package will then be automatically uploaded to [PyPI](https://pypi.org/) or
 5) Open a pull request using GitHub CLI (gh pr create) or the GitHub UI to merge the feature branch into main.
 6) After the PR is merged, delete the feature branch both locally and remotely.
 
+
 ### Example commands for the workflow:
 
 ```bash
@@ -295,7 +296,11 @@ git push origin --tags  # Push the new tag(s) created by bumpversion
 
 # 5. Open a pull request from the feature branch to the main branch
 # This can be done via GitHub UI, or using GitHub CLI
-gh pr create --base main --head feature/my-new-feature --title "New Feature" --body "This is a new feature that adds feature.txt."
+gh pr create \
+  --base main \
+  --head feature/my-new-feature \
+  --title "pr_title" \
+  --body "pr_body"
 
 # 6. After the PR is accepted and merged, delete the feature branch locally and remotely
 git checkout main  # Switch back to main branch
@@ -331,6 +336,19 @@ For further reading on the transition to `pyproject.toml` and the removal of `se
 - [PEP-518](https://peps.python.org/pep-0518/)
 - [Discussion on Setup.cfg Deprecation](https://stackoverflow.com/questions/44878600/is-setup-cfg-deprecated)
 
+#### Using GitHub CLI in Workflow Actions
+
+Easily integrate GitHub CLI into workflows to perform repository tasks. See the [GitHub CLI in workflows documentation](https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/using-github-cli-in-workflows).
+
+**Example: Create a pull request**
+
+```yaml
+- name: Create a pull request
+  run: gh pr create --title "My pull request" --body "This is an amazing PR" --label bug
+  env:
+    GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+```
+
 
 ## Common issues
 
@@ -352,7 +370,7 @@ For further reading on the transition to `pyproject.toml` and the removal of `se
 
 Which one is the key id you might ask?
 ```
-/home/user/.gnupg/secring.gpg
+/home/$USER/.gnupg/secring.gpg
 ------------------------------
 sec   4096R/<KEY_ID> 2024-11-22 [expires: 2025-11-22]
       uid                          Your Name <youremail@example.com>

{templatepy-0.2.3 → templatepy-0.2.6}/README.md

@@ -35,7 +35,7 @@
 # templatepy
 Template repo for python repositories & PyPi integration
 ---
-**Version: "0.2.3"**
+**Version: "0.2.6"**
 
 
 ## Usage
@@ -208,7 +208,6 @@ The package will then be automatically uploaded to [PyPI](https://pypi.org/) or
 
 ## Github Flow overview
 
-
 1) Create a new feature branch from main using git checkout -b.
 2) Make and commit a dummy change (e.g., adding a file).
 3) Use bumpversion to bump the version (you can adjust patch, minor, or major based on what change you want), and create a release tag.
@@ -216,6 +215,7 @@ The package will then be automatically uploaded to [PyPI](https://pypi.org/) or
 5) Open a pull request using GitHub CLI (gh pr create) or the GitHub UI to merge the feature branch into main.
 6) After the PR is merged, delete the feature branch both locally and remotely.
 
+
 ### Example commands for the workflow:
 
 ```bash
@@ -239,7 +239,11 @@ git push origin --tags  # Push the new tag(s) created by bumpversion
 
 # 5. Open a pull request from the feature branch to the main branch
 # This can be done via GitHub UI, or using GitHub CLI
-gh pr create --base main --head feature/my-new-feature --title "New Feature" --body "This is a new feature that adds feature.txt."
+gh pr create \
+  --base main \
+  --head feature/my-new-feature \
+  --title "pr_title" \
+  --body "pr_body"
 
 # 6. After the PR is accepted and merged, delete the feature branch locally and remotely
 git checkout main  # Switch back to main branch
@@ -275,6 +279,19 @@ For further reading on the transition to `pyproject.toml` and the removal of `se
 - [PEP-518](https://peps.python.org/pep-0518/)
 - [Discussion on Setup.cfg Deprecation](https://stackoverflow.com/questions/44878600/is-setup-cfg-deprecated)
 
+#### Using GitHub CLI in Workflow Actions
+
+Easily integrate GitHub CLI into workflows to perform repository tasks. See the [GitHub CLI in workflows documentation](https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/using-github-cli-in-workflows).
+
+**Example: Create a pull request**
+
+```yaml
+- name: Create a pull request
+  run: gh pr create --title "My pull request" --body "This is an amazing PR" --label bug
+  env:
+    GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+```
+
 
 ## Common issues
 
@@ -296,7 +313,7 @@ For further reading on the transition to `pyproject.toml` and the removal of `se
 
 Which one is the key id you might ask?
 ```
-/home/user/.gnupg/secring.gpg
+/home/$USER/.gnupg/secring.gpg
 ------------------------------
 sec   4096R/<KEY_ID> 2024-11-22 [expires: 2025-11-22]
       uid                          Your Name <youremail@example.com>

{templatepy-0.2.3 → templatepy-0.2.6}/pyproject.toml

@@ -4,17 +4,18 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "templatepy"
-version = "0.2.3"
+version = "0.2.6"
 authors = [
     { name = "Lars B. Rollik", email = "L.B.Rollik@protonmail.com" }
 ]
 license = { file = "LICENSE" }
-description = "templatepy: template for derivative python packages"
+description = "templatepy: Template repo for python repositories & PyPi integration"
 readme = { file = "README.md", content-type = "text/markdown" }
 classifiers = [
     "Intended Audience :: Developers",
     "Topic :: Software Development :: Libraries :: Python Modules",
     "License :: OSI Approved :: BSD License",
+    "Operating System :: OS Independent",
     "Programming Language :: Python",
     "Programming Language :: Python :: 3",
     "Programming Language :: Python :: 3.10",

{templatepy-0.2.3 → templatepy-0.2.6}/templatepy/__init__.py

@@ -1,5 +1,5 @@
 __author__ = "Lars B. Rollik"
-__version__ = "0.2.3"
+__version__ = "0.2.6"
 
 
 def run():

{templatepy-0.2.3 → templatepy-0.2.6}/templatepy.egg-info/PKG-INFO

@@ -1,7 +1,7 @@
 Metadata-Version: 2.1
 Name: templatepy
-Version: 0.2.3
-Summary: templatepy: template for derivative python packages
+Version: 0.2.6
+Summary: templatepy: Template repo for python repositories & PyPi integration
 Author-email: "Lars B. Rollik" <L.B.Rollik@protonmail.com>
 License: BSD 3-Clause License
         
@@ -38,6 +38,7 @@ Project-URL: Issue Tracker, https://github.com/larsrollik/templatepy/issues
 Classifier: Intended Audience :: Developers
 Classifier: Topic :: Software Development :: Libraries :: Python Modules
 Classifier: License :: OSI Approved :: BSD License
+Classifier: Operating System :: OS Independent
 Classifier: Programming Language :: Python
 Classifier: Programming Language :: Python :: 3
 Classifier: Programming Language :: Python :: 3.10
@@ -91,7 +92,7 @@ Requires-Dist: toml; extra == "dev"
 # templatepy
 Template repo for python repositories & PyPi integration
 ---
-**Version: "0.2.3"**
+**Version: "0.2.6"**
 
 
 ## Usage
@@ -264,7 +265,6 @@ The package will then be automatically uploaded to [PyPI](https://pypi.org/) or
 
 ## Github Flow overview
 
-
 1) Create a new feature branch from main using git checkout -b.
 2) Make and commit a dummy change (e.g., adding a file).
 3) Use bumpversion to bump the version (you can adjust patch, minor, or major based on what change you want), and create a release tag.
@@ -272,6 +272,7 @@ The package will then be automatically uploaded to [PyPI](https://pypi.org/) or
 5) Open a pull request using GitHub CLI (gh pr create) or the GitHub UI to merge the feature branch into main.
 6) After the PR is merged, delete the feature branch both locally and remotely.
 
+
 ### Example commands for the workflow:
 
 ```bash
@@ -295,7 +296,11 @@ git push origin --tags  # Push the new tag(s) created by bumpversion
 
 # 5. Open a pull request from the feature branch to the main branch
 # This can be done via GitHub UI, or using GitHub CLI
-gh pr create --base main --head feature/my-new-feature --title "New Feature" --body "This is a new feature that adds feature.txt."
+gh pr create \
+  --base main \
+  --head feature/my-new-feature \
+  --title "pr_title" \
+  --body "pr_body"
 
 # 6. After the PR is accepted and merged, delete the feature branch locally and remotely
 git checkout main  # Switch back to main branch
@@ -331,6 +336,19 @@ For further reading on the transition to `pyproject.toml` and the removal of `se
 - [PEP-518](https://peps.python.org/pep-0518/)
 - [Discussion on Setup.cfg Deprecation](https://stackoverflow.com/questions/44878600/is-setup-cfg-deprecated)
 
+#### Using GitHub CLI in Workflow Actions
+
+Easily integrate GitHub CLI into workflows to perform repository tasks. See the [GitHub CLI in workflows documentation](https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/using-github-cli-in-workflows).
+
+**Example: Create a pull request**
+
+```yaml
+- name: Create a pull request
+  run: gh pr create --title "My pull request" --body "This is an amazing PR" --label bug
+  env:
+    GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+```
+
 
 ## Common issues
 
@@ -352,7 +370,7 @@ For further reading on the transition to `pyproject.toml` and the removal of `se
 
 Which one is the key id you might ask?
 ```
-/home/user/.gnupg/secring.gpg
+/home/$USER/.gnupg/secring.gpg
 ------------------------------
 sec   4096R/<KEY_ID> 2024-11-22 [expires: 2025-11-22]
       uid                          Your Name <youremail@example.com>