The following instructions describe how to create a Git source code repository in the student.cs computing environment.
We will be using Mason GitLab for all our CS 571 coding projects, including the C systems programming projects (Linux utilities, shell, caching policies, and green threads) and Go-based distributed systems projects (Intro to Go, MapReduce, and MDFS).
IMPORTANT: There are two ways of creating a new GitLab repository. (1) Fork: You may fork the original project GitLab repositories and then immediately change the permission of the project to Private. (2) Download: Alternatively, you may create a Private project with the same project name, download the original project in a tar.gz file to your working directory, copy and upload the downloaded source code to your Private repository, and use Git to keep track of your code editing history. Leaving your repository publicly visible violates GMU Honor Code and Computer Science Department’s Honor Code policies.
For a newly created project, you can directly set the visibility to
Private upfront. For forked projects,
after the repository has been forked, go to your forked project, from
Settings, go to General, from there change Visibility level to
Private.
Next, I provide instructions for the second way of creating and populating a new GitLab repository (i.e., Download).
First, you will need to login to GitLab by clicking
Sign in with: GMU Login. Username and Password never work
for some reason.
Before cloning your GitLab repo to your computing environment (can be a student.cs (Zeus) Linux server or a cloud virtual machine server), you will need to first create an RSA SSH key by typing:
% ssh-keygen -t rsa -C "your_email_addr"
Or you can simply follow this tutorial.
Then, add an SSH key to your GitLab account by following these instructions.
Test if the SSH-based access has been successfully set.
Click on the Clone button at the right-top corner of your GitLab repo’s webpage,
copy the string under Clone with SSH to clipboard.
Then, create a new directory called cs571_proj under your $HOME directory,
cd to your working directory where you are supposed to put your project source code,
and clone your created GitLab repo on to your Linux box:
% mkdir $HOME/cs571_proj
% cd $HOME/cs571_proj
% git clone git@git.gmu.edu:your_gid/<proj_name>.git
Assuming you have already downloaded the original project locally in your $HOME directory, you can then copy the downloaded project source code into this newly created git directory:
% cd $HOME/cs571_proj/<proj_name>
% cp -r $HOME/<downloaded_proj>/* .
Now, check in the source code which you have already copied into the git directory:
% git add *
% git commit -m "init commit"
% git push
If you are checking in for the first time on an empty repo (which is your case here), you should run:
% git push -u origin master
Instead of
% git push
If you are working in a group, it is a good idea for all group members to share access to a single GitLab repo. You can enable sharing through the GitLab web interface. Hover over to Settings on the left sidebar, and click Members. Enter your team member’s Patriot ID and choose a role (Developer or Maintainer) for him/her.