Scribd
Upload
9 views2 pages

Source Code Version Control

Ananth will utilize Git for source code version control, requiring all developers to create Git accounts and upload relevant code and documentation. Gitlab groups have been established for project organization, and specific instructions are provided for project creation and code changes. Developers are advised to follow best practices for using Git, including creating branches for changes and merging them into the main branch after review.

Uploaded by

Arjun
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
9 views2 pages

Source Code Version Control

Ananth will utilize Git for source code version control, requiring all developers to create Git accounts and upload relevant code and documentation. Gitlab groups have been established for project organization, and specific instructions are provided for project creation and code changes. Developers are advised to follow best practices for using Git, including creating branches for changes and merging them into the main branch after review.

Uploaded by

Arjun
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Ananth Gitlab for Source Code

Version Control
Ananth will be using Git for source code version control. All source code
and documentation related to the code has to be uploaded to Git. All
software developers must immediately create Git accounts.
Contract IT Team for this.

Quick Links:

Gitlab Signin Url: http://git.ananthtech.com:32769/users/sign_in


Gitlab Tutorials: https://docs.gitlab.com/ee/tutorials/learn_git.html
Git with Visual Studio:
https://learn.microsoft.com/en-us/visualstudio/version-control/git-with-
visual-studio?view=vs-2022

Gitlab Groups
Digital, RF and Special Projects groups have been created on Gitlab. Do
not create sub-groups within these groups. Create your projects within
these groups. Contact Anurup first if a new group or sub-groups need to
be created.

Instructions on Project Creation


1. Create a project on the Gitlab portal using the “New Project” feature.
Projects have to be created in the related group.
2. New projects should have “Internal” visibility.
3. Add all related project members to the Project.

Instructions making code changes


Read Git related tutorials to understand how git works. Most new code
editors are coming with Git integration (for example Visual Studio Code
which is free). The free Github desktop application also works with our
Gitlab. Follow below best practice to make changes using Git (either
through the code editor or Github desktop application).

1. Clone the git repository locally. Each project in gitlab is a repository.


2. Default branch is “main” branch. Don’t make changes on main
branch. Create a new branch with a suitable name, ex: “anurup-
date-bugfix”.
3. Make file changes within the new branch.
4. Move the changed files to staging.
5. Create a commit.
6. Push the branch to “Origin” (git server). This will create your branch
in the server (ex: “anurup-date-bugfix”).
7. Goto Gitlab server web portal. Find the branch you pushed. Review
it. Share with your teammates for comments.
8. Finally merge your branch into the main branch in the server. Delete
your branch.

You might also like