Skip to content

Latest commit

 

History

History
30 lines (23 loc) · 1.14 KB

CONTRIBUTING.md

File metadata and controls

30 lines (23 loc) · 1.14 KB

Contributing to openaps

Thanks for being a part of openaps. Please submit issues and pull requests so that all users can share knowledge.

For hacking on openaps, here are some tips to help your patches reach more people more quickly. The master branch is special, it should be "production" ready code, tested and verified, and should match the contents available in pypi. Basically that means the master branch is never touched directly, but rather we use a variety of other branches to do things, and then merge the work into the master branch. Sometimes this is called git flow. Here's few guidelines that might help:

  • target a dev branch for pull requests. The latest updated branch, especially any recently updated branch with dev in the name.
  • Avoid editing master branch.
  • test changes

That's it for now, thanks again! After several successful pull requests, @bewest, @openaps and others might add you as contributor so you can create shared branches more easily.

See OpenAPS.org for background on the OpenAPS movement and project.