rm-Rf bin dist gitlab_management.egg-info lib include
rm-Rf build bin docs/_build gitlab_management.egg-info lib include pyvenv.cfg
```
>**Note:** you must increment the version in the build script (`buildinit.py`) prior to committing your final changes to the repo.
### Version Changes
Every change, prior to being committed to the `development` branch, must have it's version incremented. In most cases only the `{newfeature}` number will need to be incremented.
if the version is less than `1.0.0` the version number layout is `0.{newfeature}.{bugfix}`
if the version number is more than `1.0.0` the version number layout is `{majorchange}.{newfeature}.{bugfix}`.
`{majorchange}` should only be incremented if the end user would be required to make a manual adjustments to use the version.
To adjust the version, open `buildinit.py` and edit the `__version__` property at the top of the script.
Regardless of the version until the changes are pushed to the `development` branch, it will be adjusted to be a release candidate. the appended version information will be `.rc` with a formated date i.e. `.rcYYMMDDHHMMSS`.
## Documentation
We use Sphinx for ducumentation. All documentation for the project lives in the `docs/` directory within the repo. Documentation can be written in either RestructureText `.rst` or MarkDown `.md` files. Documentation for the modules however, is written within the code using `NumPy` style `DocBook` code comments. These comments are then rendered to `.rst` via the `sphinx.ext.autodoc` extension.
@@ -136,11 +152,18 @@ Buiding of the docs is part of the *validation* stage of the build pipeline. The
Please build the docs locally before pushing to the repo, this will ensure that they are working befor being committed. After a local build the docs can be found in the repository directory under `docs/_build/html/index.html`
Clean-up the environment prior to building the documentation, with:
``` bash
rm-Rf build bin docs/_build gitlab_management.egg-info lib include pyvenv.cfg
```
To build the documentation run:
``` bash
cd{Repo Directory}
docker run -eCI_PROJECT_DIR=/Repository -w /Repository -v$PWD:/Repository readthedocs/build:latest bash test/validation-build-docs.sh
CI_PROJECT_DIR=/Repository && docker run -eCI_PROJECT_DIR=$CI_PROJECT_DIR-w$CI_PROJECT_DIR-v$PWD:$CI_PROJECT_DIR readthedocs/build:latest bash test/validation-build-docs.sh
```
>**.. Note::**
Substitute `{Repo Directory}` with the actual directory the repository was cloned to. However, you can also miss the `cd` command and adjust `$PWD` to be the `{Repo Directory}`.
>**Tip:**
The above command contains the setting of the environmental variable `CI_PROJECT_DIR`, this is the directory where the repository is to be mounted to within the container. *don't include a trailing `/` slash if you change this.* The variable `$PWD` is to mount the current directory, if you are not running this command from the repo root dir, please set this to the full path of the repo.