|
|
@ -1 +1,21 @@ |
|
|
|
Cooperation SCM |
|
|
|
<h2>Cooperation SCM</h2> |
|
|
|
|
|
|
|
- Remote repositories are an important way to share code and collaborate. They allow you to store changes in a central location and retrieve them from other users. |
|
|
|
- There are different ways to create a remote repository and connect it to a local repository. The simplest way is to use a file-based remote repository. |
|
|
|
- The git push and git fetch commands are used to transfer changes between a local and a remote repository. |
|
|
|
- The git pull commands combine git fetch and git merge. |
|
|
|
- The git rebase command can be used to bring the local branch up to the state of another branch. |
|
|
|
- The git push --force command can be used to push changes to a remote repository, even if those changes overwrite the state of the remote repository. |
|
|
|
- The git push --force-with-lease command is a safer variant of the git push --force command. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
**Additional conclusions** |
|
|
|
|
|
|
|
- It is important to understand the consequences of the commands used when working with remote repositories. For example, the git push --force command can lead to lost changes. |
|
|
|
- It is important to use the correct configuration when working with forks. This will ensure that the changes from the fork are imported into the local repository. |
|
|
|
|
|
|
|
**Personal notes** |
|
|
|
- The exercises showed me how to use the different commands for working with remote repositories. |
|
|
|
- The exercises helped me to understand the consequences of the commands used. |
|
|
|
- The exercises showed me how forks can be used. |