Skip to content

Developer guidelines and rules #87

@kche309

Description

@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

Metadata

Metadata

Assignees

No one assigned

    Labels

    Developer RulesRules and guidelines for developers.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions