Skip to content

Latest commit

 

History

History
25 lines (14 loc) · 800 Bytes

File metadata and controls

25 lines (14 loc) · 800 Bytes

Source Control

Commits

Each commit should be one logical change.

Write descriptive commit messages. Include the reason for the change, not just what changed. Include an issue identifier if one exists.

Branches

Development should happen on the master branch.

Use branches for if releases cannot happen from master, e.g. beta and stable branches.

Avoid other long-lived branches.

Merging

Use Git Rebase

Use pull requests for code that should be reviewed or tested in CI before being merged.

Prefer rebase or merge commits. Avoid squash-merge, though they may be useful if a PR contains many changes that should not be kept in history.