Awesome that you are reading this.
This GitHub follows the Contributor Covenant Code of Conduct.
- For questions, you can create an Issue
- Code changes go via Pull Requests
beastier is part of the
babette package suite, which consists out of five packages. Here is how to determine which package is best suited for your contribution:
If you want to contribute to the creation of BEAST2 XML input files, go to beautier.
If you want to contribute to how BEAST2 output is parsed, go to tracerer
If you want to contribute regarding the BEAST2 package management, go to mauricer
If you want to contribute with an overarching idea, go to babette.
If you want to contribute to how BEAST2 is run, you are at the right spot :-)
Submitted code should follow these quality guidelines:
- All tests pass cleanly/silently
- Code coverage must be 100%
- Coding style should follow the default style by
These are all checked by Travis CI when submitting a Pull Request.
Emails with code will not be accepted.
Awesome. These are your options:
- Add an Issue, with the test that fails
- Submit a Pull Request, where the test is added to the
- Send @richelbilderbeek an email (@richelbilderbeek will make an Issue of it)
Pull Requests should follow the same guidelines as ‘Submitting code’.
masterbranch should always build successfully
developmentbranch is for developers
To get started working on
git clone https://github.com/ropensci/beastier
Development is done on the
develop branch. To download and checkout the
develop branch, first go into the
beastier folder (
cd beastier), then do:
git checkout develop
Then the workflow is the common
git pull git add --all :/ git commit -m "Did something awesome" git push