We are happy that you share your research with us and want to improve our code!
Please follow the steps below to contribute to our project.
If you have any questions or suggestions about the contributing process, please share them with us on the forum. Please note that we do not answer general questions in the github issues interface.
If you are a regular contributor in the DeepPavlov open source project, you can receive an invitation to one of our events or an opportunity to become a part of our team.
How to contribute:
Don’t start the coding first. You should do a quick search over existing issues for the project to see if your suggestion was already discussed or even resolved. If nothing relevant was found, please create a new one and state what exactly you would like to implement or fix. You may proceed with coding once someone on our team accepts your offer.
devbranch from the upstream as a base for your code:
git clone https://github.com/<OWNER>/<REPOSITORY>.git cd <REPOSITORY> git remote add upstream https://github.com/deeppavlovteam/DeepPavlov.git git fetch upstream git checkout -b dev --track upstream/dev
afterwards to sync the
devbranch with external updates you can run:
git checkout dev git fetch upstream git pull
Create a new branch and switch to it. Give it a meaningful name:
git checkout -b what_my_code_does_branch
Write readable code and keep it PEP8-ed, add docstrings and keep them consistent with the Google Style. Pay attention that we support typing annotations in every function declaration.
Accompany your code with clear comments to let other people understand the flow of your mind.
If you create new models, refer to the Register your model section to add it to the DeepPavlov registry of models.
We ask you to add some tests. This will help us maintain the framework, and this will help users to understand the feature you introduce. Examples of implemented tests are available in tests/ directory.
Please, update the documentation, if you committed significant changes to our code.
Commit your changes and push your feature branch to your GitHub fork:
git add my_files git commit -m "fix: resolve issue #271" git push origin what_my_code_does_branch
Follow the semantic commit notation for the name of the commit.
Create a new pull request to get your feature branch merged into dev for others to use. Don’t forget to reference the GitHub issue associated with your task in the description.
Relax and wait : )
Some time after that your commit will be assigned to somebody from our team to check your code. After a code review and a successful completion of all tests, your pull request will be approved and pushed into the framework.
If you still have any questions, either on the contribution process or about the framework itself, please share them with us on our forum. Join our official Telegram channel to get notified about our updates & news.