Skip to content

GitHub guidelines

Jump to bottom
Piper edited this page Oct 11, 2021 · 2 revisions

A collection of guidelines for the team to norm on, to improve overall development speed.

Develop branch

Currently, (as of October 2021) the team uses a staging branch (develop) that is cut weekly to the main trunk. The rationale for this was to have a testing environment as more stability improvements were made to the platform. All new pull requests should be open into develop.

Branching

  1. Naming doesn't matter too much. A pattern I use is fix/github-issue-number or feat/github-issue-number.
  2. Delete your branch after you merge. We would normally have GitHub do this automatically in settings, but that would automatically delete the develop branch

Join the Slack for the most up to date discussion on Climate Connect work.

Clone this wiki locally