Skip to content
Snippets Groups Projects
Commit 1e8f1883 authored by Nikita Korzhitskii's avatar Nikita Korzhitskii :bulb:
Browse files

Prettify layout of images

parent 69a94397
No related branches found
No related tags found
No related merge requests found
......@@ -29,17 +29,20 @@ These instructions describe the process of i) creating such a forked repository
Press the "Fork" button on the top of this page to copy this repository to your account.
<img src="/pictures/fork_image.png" width="500">
> <img src="/pictures/fork_image.png" width="500">
---
Then, on the next page that pops up, choose your account:
<img src="/pictures/fork2_image.png" width="500">
> <img src="/pictures/fork2_image.png" width="500">
---
After successfully forking the repository, you will see a message such as the following:
<img src="/pictures/fork3_image.png" width="500">
> <img src="/pictures/fork3_image.png" width="500">
---
### 2. Make your fork private!
......@@ -48,28 +51,28 @@ Your forked repository **must be made private** so that others do not have acces
Find the "Settings" button on the left of the page about your forked repository, and click 'General' to change the permissions for your project.
<img src="/pictures/change_permission1.png" width="500">
> <img src="/pictures/change_permission1.png" width="500">
Expand 'Permissions', set 'Project visibility' to 'Private', and then save changes.
<img src="/pictures/change_permission2.png" width="500">
> <img src="/pictures/change_permission2.png" width="500">
### 3. **Provide "Maintainer" access to your partner and your lab assistant**
Find the "Settings" button on the left of the page about your forked repository, and click 'Members' to add people who can access your repository.
<img src="/pictures/add_member1.png" width="500">
> <img src="/pictures/add_member1.png" width="500">
Follow the steps as shown in the screenshot below to provide **"Maintainer"** access to your lab partner and to your lab assistant
<img src="/pictures/add_member2.png" width="500">
> <img src="/pictures/add_member2.png" width="500">
### 4. Work on the lab assignments
You may want to download the content of your repository to the computer at which you are working on the lab assignments. If you are familiar with git, this may be done by cloning the repository on the computer. Another, perhaps easier alternative is to simply use the download option on the page about your repository as illustrated in the following screenshot; this option allows you to download a package that you have to unpack.
<img src="/pictures/download.png" width="500">
> <img src="/pictures/download.png" width="500">
After you have the content of your repository on your computer, you can start working on the lab assignments. Notice that the repository contains four folders, one for each of the four lab assignments. **Check these folders for more detailed instructions about what needs to be handed in for the corresponding lab assignment.**
......@@ -78,11 +81,11 @@ After completing an assignment, edit/upload the files to your GitLab repository.
If there exists an example report in the directory (e.g., lab1-report.txt in the directory lab1), you may open and edit the file in the browser as illustrated in the following screenshot (of course, you may also use git to push updates to this file from your computer).
<img src="/pictures/edit.png" width="500">
> <img src="/pictures/edit.png" width="500">
If there is no such file in the directory, you may upload files from your computer into the directory as the following screenshot illustrates (or, again, you may use git).
<img src="/pictures/upload.png" width="500">
> <img src="/pictures/upload.png" width="500">
### 6. Submit by sending an email with a link to the repository
To submit a solution to your lab assignment, *email a link of your repository* to your lab assistant; the subject for that email *must* adhere to the following pattern: **CourseCode_Year_labNumber_userName1_userName2**
......
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