Skip to content
Snippets Groups Projects
Commit f42e60b6 authored by Mark HOEBEKE's avatar Mark HOEBEKE
Browse files

Update git-basics/README.md

parent a8ea7aae
No related branches found
No related tags found
2 merge requests!3Merge latest from git-basics into main.,!2Update main with latest from git-basics
......@@ -116,6 +116,9 @@ Using the `Create commit...` allow to tune how modifications will be propagated
- A *merge request* will encapsulate all the modifications in a changeset and not apply them immediately to the selected branch. To actually integrate the modifications, someone will have to `Merge` (!) the merge request. A best practice is to create merge requests when a changeset is destined to another branch, especially when the destination branch is also used by other participants. When creating a merge request, GitLab allows to add more comments as well as to assign the merge request to another project participant. Depending on project configuration, developers will not be allowed to commit to some branches (typically `main` and `develop`). The will need to create a merge request if they want their changes to be integrated into these protected branches. Project maintainers will then review the merge request before actually merging the changes.
## Your Turn
Take some time to complete [the exercises](./exercises.md)
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment