-
Notifications
You must be signed in to change notification settings - Fork 37
Contribution Guide
Michał Majczak edited this page Oct 31, 2018
·
4 revisions
So you want to be PolyEngine contributor? Follow this guide.
- Join our Slack channel, for access ask @MuniuDev (michal.majczak92@gmail.com), this will also grant you an access to our trello board.
- First thing you should do is fork the PolyEngine repository. If you want, you can also download sample projects from PolyEngineExamples repository.
- Checkout
devbranch, always work on the dev branch. - Compile everything, try running unit tests or compiling one of the sample project.
- Read Coding Guidelines
- If you're ready to code then create branch that starts at the top of the up to date
dev, good practice is to name it something along the linefet/<feature-name>orfix/<fix-name>. - Develop your feature/fix on that branch.
- Push to your fork repository and create PR, with destination set to
dev. If you just want to test the CI, add[WiP]tag to the PR title. - Your PR will be reviewed as soon as all CI passes (and you removed [WiP] tag). If you want review sooner ask relevant person, see list below.