The project employs GitHub as the code commit/review system.
In brief, if you want to contribute, create or find some GitHub Issues and submit changes via GitHub Pull Requests.
- Wikipage: Lots of information and documentation about the project, e.g., meeting schedule, design doc.
- Mail List: General technical topics with Cello project.
- Fork the repository
Click the "Fork" button at the top right of the repository page.
- Clone the project to your working directory.
$ git clone https://github.com/<your-username>/cello.git
$ cd cello- Config your git name and email if not setup previously.
$ git config user.name "your name"
$ git config user.email "your email"- Create a feature branch
Always create a meaningful branch name off main:
$ git checkout -b feature/awesome-feature- After modifying the code, run
make checkto make sure all the checking is passed.
$ make check
...
py27: commands succeeded
py30: commands succeeded
py35: commands succeeded
flake8: commands succeeded
congratulations :)- Commit your code with
-sto sign-off, and-ato automatically add changes (or rungit add .to include all changes manually).
$ git commit -s -aExample commit msg may look like:
A short description of your change with no period at the end
You can add more details here in several paragraphs, but please keep each line
width less than 80 characters. A bug fix should include the issue number.
Signed-off-by: Your Name <committer@email.address>- Open a PR on https://github.com/hyperledger-cello/cello/pulls.
After the ci checking passed, wait for reviewers to approve it. The patch will be merged into the main branch after passing the review.
If you need to refine the patch further as the reviewers may suggest, you can change on the same branch, and commit the new code, and then re-request review.
This work is licensed under a Creative Commons Attribution 4.0 International License.
