Due to the size of the RevBayes project and the number of developers contributing to it, new developers should fork their own copy of the repository on GitHub, and contribute their changes via pull request.
The main branches of the RevBayes repo that should always exist are
master branch should always reflect the state of the current release of
development branch should contain the working additions/changes to the
code that are to be included in the next release.
Under normal circumstances, you should not work on either of these branches
Rather, to make changes or work on a new feature, you should create a separate
branch off of
While working on your branch, frequently merge changes from
stay up to date.
Once your work is ready, and before you merge your branch into
make sure to merge any changes from
development and verify the code is
compiling and tests are passing.
Never merge a feature branch directly into
master, the only exception being
hotfixes to the current release.
For hotfixes, create a separate branch from
master, make the fix and verify
it, and then merge the hotfix branch into