Development

Feature branch naming conventions

Feature branches must be in the format:

dev/123456789-some-ticket-description

• All feature branches must be prefixed with dev/
• 123456789 is the unique pivotal tracker id.
• some-ticket-description is a short description of the task at hand.

Quality code

Coding standards

Please adhere to best practices and any associated coding standard requirements. Coding standards are dictated per project and are not optional.

Unit tests

100% code coverage or better.

Submitting changes

Committing code

• Commit and push any code changes or additions
• Always use git status before committing files to your feature branch. Only submit relevant code
• Commit messages are important and should be descriptive of the work you have completed
• Commit messages must be in the format of [#123456] Description of the work I just coded
  • 123456 is the pivotal track id

Once your feature branch is pushed to the repository, you are ready to submit a pull request in GitHub and have your code reviewed.