A Project

report on

“Task 2”
with
Source Code Management
(22CS003)

Submitted To:
Submitted by: Name: Faculty Name: Dr.Prabhjot Kaur
Gracy Gulati Department of Computer Science &
Engineering, Chitkara University
Roll No. 2210990331 Institute of Engineering and
Technology Rajpura, Punjab

Team Member 1 Name: Gracy Gulati Roll No. 2210990331

Team Member 2 Name: Gunjan Kohli Roll No. 2210990332

Team Member 3 Name: Gunn Arora Roll No. 2210990333

Team Member 4 Name: Harleen Kaur Roll No. 2210990365

 Institute/School: - Chitkara University Institute of Engineering and
Name Technology

Department Name: - Department of Computer Science & Engineering

Bachelor of Engineering (B.E.), Computer Science&

Program Name:
-
Engineering

Source Code
Course Name: - Session: 2022-23
Management

Course Code: - 22CS003 Batch: 2022

-
Vertical Name: - First Year Group No: - G23-A

Faculty Name: Dr. Prabhjot Kaur Chahal

Signature:
Date: 27 March 2023
 Table of Content

S. Title Page No. Remarks

NO
1 Version control with Git 1

2 Problem statement 2
3 Objective 3
4 Resources Requirements – Frontend/ 3
Backend

5 Concepts and commands 4

6 Workflow and Discussion 8

7 Reference 8
VERSION CONTROL USING GIT:

Git is a version control system that is widely used in a programming

world. It is used for tracking changes in the source code.
A version control system is a tool that helps you manage "versions" of
your code or changes to your code while working with a team over
remote distances. VCS keeps track of every change in the source code
that's done over time. VCS also helps to get back the older version of
the source code.

Types of VCS

1. Local Version Control System-located in the local machine i.e. pc or

laptop.

2. Centralized Version Control System- single server center where all

files are corroborated under their names which can be collaborated with
other users also.

3. Distributed Version Control System - one or more servers and many

collaborators also each collaborator will have same copy of each
repository.

A repository is a directory or storage space where your projects can be

stored and accessed any time.
PROBLEM STATEMENT:

“Build a backend of a python project using collaborators and

deploy it on githib.”

Mini games are some of the famous two-player games played

by gamers.
First game is a guessing game in which a random number is
generated in the range given by the user and the user has to
guess the number.
Second game is a hand game in which the player randomly
chooses any of the three forms i.e. rock, paper, and scissors.
This python project is to build a game for a single player that
plays with the computer. Player can play the game in the
absence of another player.
OBJECTIVE:

The objective for this project is to associate programming with

the help of git as a repository which can be accessed and edit by
some chosen people i.e. collaborators.

1. This is required as collaborating makes the work easier,

time efficient.
2. The code becomes manageable.
3. We can get a platform to let our project be globally
accessed.

RESOURCE REQUIREMENT(BACKEND):

Python 3.5 is used with the system config of 64 bit with intel i5
processor. In python specially Jupyter Notebook is used with
the pip of random.
CONCEPTS AND COMMANDS:

STEPS:
1. Open github website, login your id, create a new repository without a readme file (scm-
project)

2. Now in the new repository go to settings and add a collaborator i.e. your team member.
3. Now go to desktop, create a new folder and initialize git in a folder, create a file(named
file1.txt), edit it using vi command, add the file to git. Now copy the file in the we created
and using command git add-A.

4. Now push the word or changes we have done. Now use cat command to whether file is
full or not, and vi editor to do some changes.
5. Now add the changed file, commit the file and check the logs.

6. Use command git revert bdb….e85 and to escape new window press esc and type “:wq”. Now
again check logs, you will see commit which revert the commit hi.
7. Now use command git reset f47….71a to reset the changes made by command git revert
and check the logs.

8. Now again push the file again using command git push -u origin main
WORKFLOW AND DISCUSSION:

REFERENCE:

1. www.google.com
2. https://github.com/
3. Collaborator- https://github.com/gunn333.git ,
https://github.com/gunjankohli30.git , https://github.com/Harleen365.git