Awesome that you are reading this.
This GitHub follows the Contributor Covenant Code of Conduct.
beautier 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 how BEAST2 is run, 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 the creation of BEAST2 XML input files, you are at the right spot :-)
Use cases within the default BEAUti environment are welcomed.
Please send all that is needed to reproduce the use case:
BEAUti plugins are not supported (for now). See ‘Submitting code’ if you’d like
beautier to do so.
You can do so by:
Submitted code should follow these quality guidelines:
These are all checked by Travis CI when submitting a Pull Request.
For BEAUti plugins, there needs to be added:
Emails with code will not be accepted.
Awesome. These are your options:
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/beautier
Development is done on the
develop branch. To download and checkout the
develop branch, first go into the
beautier folder (
cd beautier), then do:
git checkout develop
Then the workflow is the common
git pull git add --all :/ git commit -m "Did something awesome" git push