Thank you for investing your time in contributing to our project!
Please read our Code of Conduct to keep our community approachable and respectable.
In this guide you will get an overview of the contribution workflow from opening an issue, creating a PR, reviewing, merging the PR and releasing.
To get an overview of the project, read the README.
If you spot a problem with the docs, search if an issue already exists. If a related issue doesn't exist, you can open a new issue using a relevant issue form.
Scan through our existing issues to find one that interests you. You can narrow down the search using labels as filters. You can also take a look at the open milestones to have an idea of the issues priorities. To follow the progress of issues, let's take a look the projects
As a general rule, we don’t assign issues to anyone. If you find an issue to work on, you are welcome to open a PR with changes to solve it.
- Fork the project.
- Checkout a new branch (
git checkout -b feature/amazing-feature). - Implement your solution following our code conventions
- Commit and push your changes (
git add .; commit -m 'feat(blockchain): add some amazing feature'; git push origin feature/amazing-feature). - Create a pull request (PR) targeting the
mainbranch.
🛡 Restricted to write access members.
The tags and releases are automatically created using semantic-release each time a commit is pushed on the main branch.
The packages are automatically pushed.
The versioning follows the semantic versioning convention.
The commit messages on the main branch must follow the Angular commit message format and finish with the PR number (ie fix(ui): message (#1))
We try follow the Golang clean code conventions.