noteId | tags |
---|---|
0d1b7090b1d311eb8c4ed19e49359bd0 |
Welcome; we appreciate you and would like to thank you for contributing to our project. This document aims to facilitate the process and share with you some structure that hopefully will remove any roadblock.
- Each reported issue shall have a name and description.
- It should also have a detailed description of the requested feature.
- It should include the expected solution.
- The issue shall be reviewed and approved by one of the collaborators in the projects before any contributor starts working on it.
- The issue discussion shall include the basics principles of communication.
- It should be clear, and if a solution is proposed, it should include pros and cons.
- If a question is asked, it should tag at least one of the project collaborators who will provide some guidance around the issue and/or the solution
- The PR shall include a clear description of the proposed solution
- If there is any additional information or link, it shall be included in the description.
- The PR has to pass all tests and build stages;
- if new features are added, these HAVE to be tested
- (Optional) The contributor has the option to include the Twitter handle.
$ git clone [email protected]:YOUR-USERNAME/YOUR-FORKED-REPO.git
$ cd into/cloned/fork-repo
$ git remote add upstream git://github.com/ORIGINAL-DEV-USERNAME/REPO-YOU-FORKED-FROM.git
$ git fetch upstream
$ git checkout master
$ git pull --rebase upstream master
$ git checkout your-branch
$ git pull --rebase master
$ npm install
$ npm run build
$ npm run ganache:start
$ npm run test
$ git add .
$ git commit -m "MESSAGE"
$ git push origin master
If you have any comment or ideas in terms of making this process better, please let us know or submit a PR.