Practices

Merge Request

Description

• Put a good description, as a good commit message

  • Do squash or ask branch to be squashed

Milestones

• Always use milestones

• Easier to track project development

• Easier to track sprint progress

Use Tags

• Easier for code reviews to have some context

• Easier to search for issues                        

Context

If you have a team work ticket, reference it

Team work / Gitlab Ticket

• Reference it in your branch name
• Reference it in your commit message / MR title

Preview

If you’re doing a frontend change (HTML/CSS)

MR with Preview

New configs?

• Put the default configs in the MR

• Update all geos’ configurations

Workflow

Code Review

• Ask your MR to be reviewed by assigning them'​

• @fdx

• @vemec

Code Review

• If you need peer-review

• @ in a comment

As usual

• Work on a feature/hotfix/task branch

• Merge back to where it comes from:

  • Features -> Develop

  • Hotfix/Task -> Master

Operatives

• Take the time to create a HOW TO in our Gitlab Wiki

How To's Wiki page

http://gitlab.afluenta.com/afluenta/afluenta-platform/wikis/how-to-s