Datasheet

Commit and push

Once you have your repo set up, edit files as usual. Whenever you get to a stable state, or just every now and

then to keep history and insure against losing your work, push the changes to GitHub. This is done with a little GitHub

sync button on top of the Explorer. The button will check if there are any pending changes to check in. If there are, it

will create a commit, pull the latest changes from GitHub, merge or fast-forward the commit if needed, and push the

results to GitHub.

If there are changes, you will be asked for a commit message. Try to write something meaningful, like

Fixed temperature reading in sub-freezing conditions or Added mysensor.readTemperature() function .

When describing changes, you are also given an option to bump the version number. This is a signal that the version

you're pushing is stable and the users should upgrade to it. When your package is first referenced, the latest bumped

version is used. Similarly, if there is a newer bumped version, a little upgrade button will appear next to the package.

Commits without bump are generally not accessible to most users, so they are mostly for you to keep track of things.

We do not really distinguish between a commit, push, and pull - it all happens at once in the sync operation.

You can view a history of changes by following the version number link on the Project Settings page.

https://learn.adafruit.com/adafruit-feather-m0-express-designed-for-circuit-python-

circuitpython

Page 186 of 199