Select git workflow for development

[magicDGS]

• Git Feature Branch
• Gitflow

[heuermh]

For Big Data Genomics organization projects, we use something like Git Feature Branch, with the following:

• Intermediate/insignificant commits on pull request branches should be squashed
• Pull requests are merged to master with the Github Rebase and Merge button
• Pull request authors cannot merge their own pull requests
• Pull requests cannot be merged until the CI build passes
• Pull requests and commits are linked to issues whereever possible (e.g. Fixes #foo)
• Releases use a process based on the Maven Release Plugin, which creates release tags and release branches

[magicDGS]

@heuermh - your comment in the initial code contribution about the branch from the repo instead of a fork (#14 (comment)) is related with this guidelines about the git-workflow.

Maybe we can somehow disable making branches in the repo, or enforce every commiter (including maintainers) to use their own fork. That will also keep the branchs in the repo clean and open only if necessary (e.g., master and gh-pages)

[heuermh]

Decisions/recommendations made here should be added to CONTRIBUTING.md.

[heuermh]

Fixed by #98