beetools 5.1.1

Tools for batch scripts, virtual environments and utilities.

General
CI
PyPI
Github

Designed for the use in the Bright Edge eServices echo system. It defines methods and functions for general use purposes.

Installation

pip install beetools

Tests

1. This project uses pytest to run tests.

2. There are various settings combinations in the [tool.pytest.ini_options] section of the pyproject.toml file that can used by commenting it out.

3. This project uses black to format code and flake8 for linting. We also support pre-commit to ensure these have been run. To configure your local environment please install these development dependencies and set up the commit hooks.

pytest

Contributing

Naming Conventions

1. Branch names

   “enhancement” | “bug” | “hotfix”/< ticket_nr>_<description>

   where

   enhancement - Planned improvement or addition to functionality; non-urgent.

   bug - An error or defect causing incorrect or unexpected behavior; typically fixed in regular development cycles.

   hotfix - An urgent, critical fix applied directly to the live environment, often bypassing regular development cycles.

   ticket_nr: Ticket number assigned to the issue in GitHub. Once an issue is registered, the owner will assign a ticket.

   description: GitHub issue title or combination of titles is more than one issue is addressed.

Releasing

For the purpose of push and release of code two script files are included. Use there two files to files to make life a bit easier. The scripts make use of the gitit module to simplify tasks.

1. push.bat - Use this script to push branches to GitHub repository. In principle it does the following:

   usage: push message

   e.g. push “Changed the Infinite Improbability Drive”

   1. .rst syntax check

   2. git add -A

   3. git commit -m message (with pre-commit including black and flake8)

   4. git push –all

2. release.bat - Use this script to push a new tag and release to the GitHub repository. Remember to change the version number in the setup.cfg else the workflow will fail.

   usage: release version The version will match the release and the tag. Only issue a release once a push.bat was successful. In principle it does the following:

   e.g. release 1.2.3

   1. Commit the changes

   2. Create and push the release tag with the correct naming conventions.

   3. Checkout master since it assumes that the branch is now merged with master and will be deleted.

   4. display a list of all the current branches as a reminder to delete the branch on completion.