ℹ️ You should avoid pushing your work until you’re happy with it and ready to share it with the rest of the world (git-scm.com).

Conventional commits

We are using conventional commits v1.0.0, please refer to the online documentation. Into the git message you can also add references about the GitLab issues that you are working on.

Here a basic example of how you can use it.

fix: init only one time the InputService

Service restarted every time when the cursor moved.

Refs: https://gitlab.e.foundation/e/backlog/-/issues/3316

Rewriting history

The git history is important, in order to know easily changes done into a given project. When a new contributor discovering the project by reading the git history he should be able to understand some choices or figure out a commit which can lead to a regression.

So to ensure that the git history reflects the work done it is important to be able to rewrite the commits history of your development branch before to submit it or when a reviewer will make some comments. We don’t want to introduce commits message like lint or apply review suggestion. Such commit has to be squashed.

Here an online documentation for helping you to rewrite you git history.