To manage new features, bug-fix and release we use Git-Flow. External contributions can be submitted through Github Pull Requests.
master branch is used for production (i.e., features ready for the public to use).
develop branch is used to merge intermediate features during before releasing to the
feature/$FEATURE_NAME branches are used to develop each intermediate feature (many can be used in parallel).
For other developers, it is better to use Github Pull Requests so that the submitted code can be reviewed by maintainers of the repository. The first, step is to fork the github repository (i.e., do not forget to “synchronise” your fork regularly with the main repository), then develop new features the
develop branch and once completed or well advanced submit it to the main repository
The installation of the development dependencies (e.g., code formatting, linter, documentation) uses the
[dev] marker. It is also important to install the _pre-commit_ environment before starting to develop to run static code-checks (e.g., syntax and format) before each commit.
git clone -b develop firstname.lastname@example.org:deephyper/deephyper.git cd deephyper/ pip install -e ".[dev]" pre-commit install
Code Formatting (Black)#
The code needs to be formatted with Black which should be installed through the _pre-commit_. For a manual usage it can be installed with
pip install black. Then to check the diff you can do the following from the root of the repository:
black --diff --check $(git ls-files '*.py')
And to apply the formatting you can do from the same location:
black $(git ls-files '*.py')
It is important to note that files not yet added to the git tree will not be processed by the previous commands.
The linter used is Flake8. The linter can be launched with:
To ignore a specific linter directive the `` # noqa: F541`` can be used.
The list of Flake8 rules can be found here.
The configuration of flake8 is located in the at
`deephyper/setup.cfg under the