#Git config color ui update
#Git config color ui code
#Git config color ui password

Keep your password safe, but don't forget it! You should note it down somewhere safe and keep it with you as you will need it to unlock the SSH key in future. So DO NOT share the key, or your password that you used to lock the key. The purpose of the SSH key is for you to authenticate that you are who you say you are to the server. We assume you are using a NARGA machine in Ubuntu, but these instructions should be applicable for any Linux machine. Next, we will need to add your SSH key so that you can clone a copy of the project repository (or repo for short) to your local PC. If you have been enrolled in a course that uses GitLab for projects, you should see the projects listed on this page. You won't be able to create any projects or groups as an undergraduate, but if you are a postgraduate, you can request permissions for this. You will be re-directed to the Microsoft office OAuth system to log in with your Univerisy credentials.Ĭongratulations! You should now be logged in. Now click the US Office365 button encircled in red in the below image. Navigate to, or click here to open the login page in a new tab.GitLab has been set up such that you can log in with your Stellenbosch University credentials. Otherwise, when in doubt, ask your lecturer. Here is a reference for general student responsibilities:

#Git config color ui code

Please refer to your module guidelines in regard to code sharing and see the plagiarism declaration for your course. What is Git and GitLab? ¶Ī secure copy is not a public project on GitHub or any other hosting service. This section is aimed towards first time users of both Git and this instance of GitLab. Replace all local changes with the server version. Replace the changes in the file with the last content in HEAD. Un-stage changes to a file that have been git added. Send the commits on your local machine to the GitLab server Move the changes from the staging area to HEAD on your local machine Show changes from the file or all files if none specified.Īdd the specific file or directory to the staging area. Show the current status of the local working tree.

#Git config color ui update

Simple Git Commands ¶ Commandįetch the latest commits from the GitLab server and update your local repository. Remove the -global to apply the settings to only the current project. In the sections below, -global implies changes will be applied to all projects. Set the default commit message editor to vim. Git config -global core.editor 'gedit -s' Set up git to push only the current branch by default. Set up the email address for your commits. Git config -global user.email 'YOUR_EMAIL' Git config -global user.name 'YOUR_USERNAME'

git push to send local changes to GitLab.

git commit to move changes from the index to a local commit.

git add files to the index (staging area).

Make changes to your local files in the repository.

git pull to bring changes from GitLab to the local repository.

The above is a very good summary, and you are encouraged to have it open or printed out for your reference.

Cheat SheetĪ more complete 'cheat-sheet' can be found here. This is a quick reminder of the basic commands. If you are looking for GitLab's docs, they are here.

If this is your first time using Git or simply using this GitLab server, please read through First time using GitLab before anything else.