Skip to content
Snippets Groups Projects
Commit df3a9f39 authored by Michael Martins's avatar Michael Martins
Browse files

Fixed repo name

parent b445d4c0
No related branches found
No related tags found
No related merge requests found
......@@ -92,10 +92,10 @@ If pushing to your repository does not work for whatever reason, please print ou
* Open a command line/terminal and clone your repository. The command should look something like:
```
git clone git@gitlab.uni-hannover.de/<your_username>/dalab_2024.git
git clone git@gitlab.uni-hannover.de/<your_username>/data_analysis_lab_2024.git
```
This will automatically create a new folder called `dalab_2024` inside the folder where you ran the command and will give you an error if such a folder exists. If you want the folder to have another name run `git clone git@gitlab.uni-hannover.de:<your_username>/dalab_2024 <new_folder_name>`, e.g: `git clone git@gitlab.uni-hannover.de:name.lastname/dalab_2024 new_awesome_name`. If you want to move the entire folder after you have cloned it, everything will work fine as the git references are kept in hidden files inside the folder.
This will automatically create a new folder called `data_analysis_lab_2024` inside the folder where you ran the command and will give you an error if such a folder exists. If you want the folder to have another name run `git clone git@gitlab.uni-hannover.de:<your_username>/data_analysis_lab_2024 <new_folder_name>`, e.g: `git clone git@gitlab.uni-hannover.de:name.lastname/data_analysis_lab_2024`. If you want to move the entire folder after you have cloned it, everything will work fine as the git references are kept in hidden files inside the folder.
#### Your first commit
......@@ -132,15 +132,15 @@ To get new changes that are pushed to __this__ main repository the simplest way
<details>
<summary>Solution here</summary>
Go to your `dalab_2024` folder.
Go to your `data_analysis_lab_2024` folder.
To see what repositorities you are tracking run `git remote -v` - The output will probably look like this
```
$ git remote -v
origin git@gitlab.uni-hannover.de:<your_username>/dalab_2024.git (fetch)
origin git@gitlab.uni-hannover.de:<your_username>/dalab_2024.git (push)
origin git@gitlab.uni-hannover.de:<your_username>/data_analysis_lab_2024.git (fetch)
origin git@gitlab.uni-hannover.de:<your_username>/data_analysis_lab_2024.git (push)
```
Because you did the fork from the interface you can also get the new changes from the interface. But the better way to it is to add a _'remote'_ pointing to the fork (Add a keyname for the main repository). The textbook name for a repo you forked from is __upstream__.
Add a remote named _upstream_ pointing to *this* repo using: `git remote add upstream git@gitlab.uni-hannover.de:gianluca.pagliaro/dalab_2024.git`. Now when you run `git remote -v`you should see something *like* this:
Add a remote named _upstream_ pointing to *this* repo using: `git remote add upstream git@gitlab.uni-hannover.de:gianluca.pagliaro/data_analysis_lab_2024.git`. Now when you run `git remote -v`you should see something *like* this:
```
$ git remote -v
origin git@gitlab.uni-hannover.de:<your_username>/dalab_2024.git (fetch)
......
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