Create a repository

Once you create a new project, you can add new files via UI
(read the section below) or via command line.
To add files from the command line, follow the instructions that will
be presented on the screen when you create a new project, or read
through them in the command line basics
documentation.

Find files

Branches

When you submit changes in a new branch, you create a new version
of that project's file tree. Your branch contains all the changes
you are presenting, which are detected by Git line by line.

To continue your workflow, once you pushed your changes to a new branch,
you can create a merge request, perform
inline code review, and discuss
your implementation with your team.
You can live preview changes submitted to a new branch with
Review Apps.

To learn more about branching strategies read through the
GitLab Flow documentation.

Commits

When you commit your changes,
you are introducing those changes to your branch.
Via command line, you can commit multiple times before pushing.

Commit message:
A commit message is important to identity what is being changed and,
more importantly, why. In GitLab, you can add keywords to the commit
message that will perform one of the actions below:

Trigger a GitLab CI/CD pipeline:
If you have your project configured with GitLab CI/CD,
you will trigger a pipeline per push, not per commit.

Skip pipelines:
You can add to you commit message the keyword
[ci skip]
and GitLab CI will skip that pipeline.

Cross-link issues and merge requests:Cross-linking
is great to keep track of what's is somehow related in your workflow.
If you mention an issue or a merge request in a commit message, they will be shown
on their respective thread.