Skip to content

Commit bb51eab

Browse files
resolved conversation
1 parent 81e06b0 commit bb51eab

File tree

2 files changed

+17
-13
lines changed

2 files changed

+17
-13
lines changed

doc/user_guide/features.rst

Lines changed: 9 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,13 @@
11
Features
22
========
33

4-
Uniformed Project Layout
5-
------------------------
4+
Uniform Project Layout
5+
----------------------
66

7-
Overall, the toolbox generally expects a certain project layout because it tries to follow the credo "convention over configuration" when possible and reasonable. This expected structure can be better understood by looking at the cookie-cutter project template, which is part of the python-toolbox workspace and can be found in `project-template`. One can also generate a project from the template to explore the default structure. For more details on this, please check out the getting started section.
7+
PTB expects a default project layout following "convention over configuration" when possible and reasonable.
8+
See the cookie-cutter project template for details, which is part of the python-toolbox workspace and can be found in directory `project-template`.
9+
You can also generate a project from the template to explore the default structure.
10+
For more details on this, please check out section `"getting started" <getting_started.html>`_ section.
811

912
Nox
1013
---
@@ -20,9 +23,9 @@ Central files in regards to nox and the toolbox are:
2023
Important Nox Commands
2124
^^^^^^^^^^^^^^^^^^^^^^
2225

23-
* :code:`nox -l` this command shows a list of all available nox tasks
24-
* :code:`nox -s <tasks>` to run the specified task(s)
25-
* :code:`nox -s test:typing` which runs the type checker on the project
26+
* :code:`nox -l` shows a list of all available nox tasks
27+
* :code:`nox -s <tasks>` run the specified task(s)
28+
* :code:`nox -s test:typing` runs the type checker on the project
2629
* :code:`nox -s docs:clean docs:build docs:open`
2730
#. first task removes the documentation folder
2831
#. second one builds the documentation

doc/user_guide/how_to_release.rst

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,12 @@
11
How to Release
22
==============
33

4-
#. Use the command :code:`nox -s release:prepare` to prepare the project for a new release.
5-
#. Merge your **Pull Request** to main
6-
#. Switch the **current branch** to the **default branch**
7-
#. Ensure default branch to be up to date: :code:`git pull`
8-
#. Set your **tag name**: :code:`TAG=<name>`
4+
#. Use :code:`nox -s release:prepare` to prepare the project for a new release.
5+
#. Merge your **Pull Request** to the **default branch**
6+
#. Use :code:`git remote show origin | sed -n '/HEAD branch/s/.*: //p'` to output the **default branch**
7+
#. Use :code:`git checkout <default branch>` Switch to the **default branch**
8+
#. Use :code:`git pull` to update branch
9+
#. Use :code:`TAG=<name>` to set a variable named **"TAG"**
910
#. Use :code:`git tag "${TAG}"` to create a new tag in your repo
10-
#. Use :code:`git push origin "${TAG}"` to push it in your remote repo
11-
#. GitHub workflow reacts on this tag and starts the release process
11+
#. Use :code:`git push origin "${TAG}"` to push it to remote
12+
#. GitHub workflow **CD** reacts on this tag and starts the release process

0 commit comments

Comments
 (0)