Developer guidelines and rules

[kche309]

Update: Tutorial on coding guidelines
https://github.com/kche309/CodeDemo/blob/main/code-style.pdf

Create documentation for developer guidelines and git processes.

Requirement: Provide example workflow of "developing a new feature" and list resources and developer rules.
Goal: Ensure repository is stable and master branch remains working.

Best practices including but not limited to:

• Only commit working code to master!
• Using a branch or fork when developing a new feature or bugfix
• Commit changes often and frequently to your branch/fork
• Use Camel-case naming for Java
• Link to your Git Issue in your commits

To be added to current dev resources here
https://github.com/bioDS/beast-phylonco/tree/master/developer-guide

[kche309]

Useful Git resources

How to create forks
https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo

How to make a pull request
https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request