Gitlab Setup (team)
- In preparation of this activity every team member must have completed the individual GitLab Access and Setup. If you have created your (PAT) and have confirmed that you have login access to your teammates, then you are ready. Notify your instructor immediately if you cannot access the site with your RIT credentials. You may need to reach out to gccisit@rit.edu for assistance.
- The assignment requires good coordination between team members. As a first step, you will need to select one team member that has confirmed access to the above site and who will help in preparation of your repository. We will call this person the Configuration Coordinator (CC). Let the instructor know who that person will be for your team.
* DO NOT proceed with the following Gitlab activities UNTIL GIVEN DIRECTIONS from Your Instructor
Instructions: ONLY Configuration Coordinator (CC)
These instructions are ONLY to be completed by the Configuration Coordinator (CC). Not complying with this will cause serious problems and may result in penalties.
- Download the create repository CC instructions and follow them rigorously.
- if something doesn't work as intended and you cannot figure it out, ask for help of your TA or your instructor (but as before, in virtually every case it happens when you missed something or didn't follow the instructions precisely).
Instruction for: ALL Other Team Members
- While the Configuration Coordinator is doing the setup, other team members should review the version control concepts and discuss the ways in which you would like your team to collaborate in using the repository
- how will you coordinate working on the code and artifacts?
- what should be communicated and when?
- what responsibilites do you each have and what type of support do you want from your Configuration Coordinator (CC).
- Consider what agreements should be added to your Team Contract and make the updates.
- Once your Configuration Coordinator tells you that the repository is ready:
- download and follow the All Team members instructions to fork and use the repository. Be sure to follow them rigorously.
- if something doesn't work as intended and you cannot figure it out, ask CC for help or reach out to TA or instructor (but as before, in virtually every case it happens when you missed something or didn't follow the instructions precisely).
Submission
After all team members have completed the setup and used their Visual Studio Code IDE to add their names to the project README.mdfile:- capture the log for the repository (make sure it is up-to-date with remote) using the command git log > github.txt,
- or by copy-and-paste of the log command output in the terminal window into a github.txt file. (It should look something like the image below)
Example output is shown below.
commit d03fc4b90ab35589c8445df0b94da65204708941
Merge: 4850e5d a4fdfd9
Author: Nicole Minton <nnm3367@rit.edu>
Date: Mon Sep 25 08:34:38 2028 -0400
Resolved conflict.
commit 4850e5daf7487f0512dea550b2d43e10cc38c67d
Author: Nicole Minton <nnm3367@rit.edu>
Date: Mon Sep 25 08:31:00 2028 -0400
Nicole added name
commit a4fdfd9b0b72ba7a8b19efdd445de05991b413fc
Author: Caitlin Klein <csk6489@rit.edu>
Date: Mon Sep 25 08:30:29 2028 -0400
Caitlin checking in
commit c778d914eb1a9d3092287e4577152cfeeffaca32
Merge: 98a0f1c 84ed6a8
Author: Joe Bills <jcb1234@rit.edu>
Date: Mon Sep 25 08:26:39 2028 -0400
Resolved conflict
commit 98a0f1c128dea0359f0dc34f70ddc891d5589979
Author: Joe Bills <jcb1234@rit.edu>
Date: Mon Sep 25 08:18:16 2028 -0400
Joe's name
commit 84ed6a8b9a6d2aa34ef6bbf21f766bdee78e7c7c
Author: Jimmy Veliagno <J.Veliagno@se.rit.edu>
Date: Mon Sep 25 08:13:19 2028 -0400
Jimmy
commit 1e2e69b9829f011b0a37ac46c4b0ccb518a81dee
Author: Jimmy Veliagno <J.Veliagno@se.rit.edu>
Date: Mon Sep 25 07:49:57 2028 -0400
First commit