From dd0791f5e8b62375dc252af2c5fe9100abe06f83 Mon Sep 17 00:00:00 2001
From: FlorianWilhelm
Start your work on this branch. Don't forget to add docstrings in Google style to new functions, modules and classes, especially if they are part of public APIs.
Add yourself to the list of contributors in AUTHORS.md
.
When you’re done editing, do:
git add <MODIFIED FILES>
git commit
Info
Don't forget to add unit tests and documentation in case your contribution adds a feature and is not just a bugfix.
Moreover, writing an descriptive commit message is highly recommended. In case of doubt, you can check the commit history with:
git log --graph --decorate --pretty=oneline --abbrev-commit --all
-
Please check that your changes don't break any unit tests with hatch run test:cov
or hatch run test:no-cov
to run the unitest with or without coverage reports, respectively.
hatch run lint:all
in order to run flake8, isort, black, mypy, etc.git push -u origin my-feature
+
Please check that your changes don't break any unit tests with hatch run cov
or hatch run no-cov
to run the unitest with or without coverage reports, respectively.
hatch run lint:all
in order to run flake8, isort, black, mypy, etc.git push -u origin my-feature
Find more detailed information in creating a PR. You might also want to open the PR as a draft first and mark it as ready for review after the feedbacks from the continuous integration (CI) system or any required fixes.
Even though these resources focus on open source projects and communities, the general ideas behind collaborating with other developers to collectively create software are general and can be applied to all sorts of environments, including private companies and proprietary code bases. ↩