Skip to content

Latest commit

 

History

History
116 lines (76 loc) · 4.06 KB

CONTRIBUTING.md

File metadata and controls

116 lines (76 loc) · 4.06 KB
Raw

How to contribute to this project

Hercules is a project from the community and for the community. So we welcome all kinds of contributions:

  • Technical contributions: Review the instructions below and feel free to open a PR.
  • Want to start small? No problem. Contribute to documentation, build a tool, recreate a bug. We all started in one of these places.
  • Organize a local meetup, talk to people, or answer a question: The power lies in your hands. 💪

You need PYTHON3!

These instructions are for linux base systems. (Linux, MacOS, BSD, etc.)

Setting up your own fork of this repo.

  • On github interface click on Fork button.
  • Clone your fork of this repo. git clone [email protected]:YOUR_GIT_USERNAME/testzeus-hercules.git
  • Enter the directory cd testzeus-hercules
  • Add upstream repo git remote add upstream https://github.com/test-zeus-ai/testzeus-hercules

Setting up your own virtual environment

Run make virtualenv to create a virtual environment. then activate it with source .venv/bin/activate.

Install the project in develop mode

Run make install to install the project in develop mode.

Run the tests to ensure everything is working

Run make test to run the tests.

Create a new branch to work on your contribution

Run git checkout -b my_contribution

Make your changes

Edit the files using your preferred editor. (we recommend VIM or VSCode)

Format the code

Run make fmt to format the code.

Run the linter

Run make lint to run the linter.

Test your changes

Run make test to run the tests.

Ensure code coverage report shows 100% coverage, add tests to your PR.

Commit your changes

This project uses conventional git commit messages.

Example: fix(package): update setup.py arguments 🎉 (emojis are fine too)

Push your changes to your fork

Run git push origin my_contribution

Submit a pull request

On github interface, click on Pull Request button.

Wait CI to run and one of the developers will review your PR.

Makefile utilities

This project comes with a Makefile that contains a number of useful utility.

❯ make
Usage: make <target>

Targets:
help:             ## Show the help.
show:             ## Show the current environment.
install:          ## Install the project in dev mode.
fmt:              ## Format code using black & isort.
lint: fmt             ## Run pep8, black, mypy linters.
test: lint        ## Run tests and generate coverage report.
watch:            ## Run tests on every change.
clean:            ## Clean unused files.
virtualenv:       ## Create a virtual environment.
release:          ## Create a new tag for release.
build:       ## build testzeus_hercules.
publish:          ## Publish the package to PyPI.
run:       ## run testzeus_hercules.
run-interactive:       ## run-interactive testzeus_hercules.
setup-poetry:       ## setup poetry.
docker-build:       ## build and tag docker image.
docker-publish:          ## Publish the package to Docker registry.

Making a new release

This project uses semantic versioning and tags releases with X.Y.Z Every time a new tag is created and pushed to the remote repo, github actions will automatically create a new release on github and trigger a release on PyPI.

For this to work you need to setup a secret called PIPY_API_TOKEN on the project settings>secrets, this token can be generated on pypi.org.

To trigger a new release all you need to do is.

  1. If you have changes to add to the repo
  2. Run the tests to ensure everything is working.
  3. Run make release to create a new tag and push it to the remote repo.

the make release will ask you the version number to create the tag, ex: type 0.1.1 when you are asked.

CAUTION: The make release will change local changelog files and commit all the unstaged changes you have.