{"id":69,"date":"2024-07-30T06:49:31","date_gmt":"2024-07-30T06:49:31","guid":{"rendered":"https:\/\/libraryresources.nse.org.ng\/computersciencetwo\/chapter\/installing-and-configuring-git\/"},"modified":"2026-03-16T14:29:17","modified_gmt":"2026-03-16T14:29:17","slug":"installing-and-configuring-git","status":"publish","type":"chapter","link":"https:\/\/libraryresources.nse.org.ng\/computersciencetwo\/chapter\/installing-and-configuring-git\/","title":{"raw":"Installing and Configuring Git","rendered":"Installing and Configuring Git"},"content":{"raw":"
\n

Lecture: Installing Git on MacOS<\/a><\/p>\n

Lecture: Configuring VSCode with Git<\/a><\/p>\n

<\/p>\n

Download Git<\/a> - Visit this website to download Git for your operating system.<\/p>\n

<\/p>\n

Choose your operating system and download the latest stable release.<\/p>\n

\"image\"<\/p>\n

<\/p>\n\n

<\/a>Downloading Git for MacOS<\/h3>\n

Click on macOS. It should take you to a page with instructions for installing Git.<\/p>\n

\"image\"<\/p>\n

<\/p>\n

Open a terminal by pressing \"Command + Space\" and type \"terminal\". Choose the application named Terminal.<\/p>\n

\"image\"<\/p>\n

<\/p>\n

If you don't already have it, install Homebrew by copying the line of code on the Homebrew site<\/a>. Paste it into the terminal and press enter. If you don't know if you have it or not, try installing Git and if it fails, install Homebrew.<\/p>\n

<\/p>\n

\"image\"<\/p>\n

<\/p>\n

Don't forget to run the commands given by Next Steps after Homebrew is installed.<\/p>\n

\"image\"<\/strong><\/p>\n

<\/p>\n

Install Git by running brew install git<\/p>\n

\"image\"<\/p>\n

<\/p>\n

Run git on the command line to ensure it was installed successfully.<\/p>\n

To run git, type git and press enter.<\/p>\n

\"image\"<\/p>\n

<\/p>\n

If git runs, you're done! If not, make sure you installed Homebrew correctly, including adding brew to your PATH.<\/p>\n\n

<\/a>Downloading Git for Windows<\/h3>\n

After the installer downloads, run the installer. Click Next.<\/p>\n

\"image\"<\/p>\n

<\/p>\n

The default path is fine. Click Next.<\/p>\n

\"image\"<\/p>\n

<\/p>\n

If you want a Desktop Icon, check the box next to \"On the Desktop\". You won't really need to run the Git GUI, so you probably won't directly run this program. You likely won't need the icon, but that's up to you.<\/p>\n

<\/p>\n

If you want to be able to right click and see \"Open Git Bash\" or \"Open Git GUI\" from the file explorer, check the boxes next to<\/p>\n

Windows Explorer integration<\/p>\n

Open Git Bash here<\/p>\n

Open Git GUI here<\/p>\n

<\/p>\n

Make sure to check the boxes next to<\/p>\n

Git LFS<\/p>\n

Associate .Git* configuration files with the default text editor<\/p>\n

Associate .sh files to be run with Bash<\/p>\n

Add a Git Bash Profile to Windows Terminal<\/p>\n

<\/p>\n

Uncheck the box next to<\/p>\n

Scalar (Git add-on to manage large-scale repositories)<\/p>\n

<\/p>\n

Click Next.<\/p>\n

\"image\"<\/p>\n

\"image\"<\/p>\n

<\/p>\n

<\/p>\n

Choose what you want to name the shortcuts in your Start Menu or click \"Don't create a Start Menu folder\" if you don't want the shortcut. Click Next.<\/p>\n

\"image\"<\/p>\n

<\/p>\n

Choose \"Visual Studio Code as Git's default editor\". Click Next.<\/p>\n

\"image\"<\/p>\n

<\/p>\n

Either of these options is fine. Traditionally, your main branch on Git is named the \"master branch\". Branches are how you test out features; you switch branches to make a copy of the code to toy around with features without breaking the main build. When your feature is ready, you merge it back onto the \"master branch\". However, recently, this has come up as perhaps inappropriate, and so Git is working to rename it.<\/p>\n

<\/p>\n

If you want to rename your main branch now, choose the second option. If you want to leave it until Git officially renames it, choose the first option. Either option is fine.<\/p>\n

<\/p>\n

Click Next.<\/p>\n

\"image\"<\/p>\n

<\/p>\n

Choose \"Git from the command line and also from 3rd-party software\". You need to check this so that VS Code can access Git.<\/p>\n

\"image\"<\/p>\n

<\/p>\n

Choose \"Use bundled OpenSSH\". Click Next.<\/p>\n

<\/p>\n

\"image\"<\/p>\n

<\/p>\n

Choose \"Use the OpenSSL library\". Click Next.<\/p>\n

\"image\"<\/p>\n

<\/p>\n

Choose \"Checkout as-is, commit Unix-style line endings\". This helps preserve formatting when getting code to and from GitHub. Click Next.<\/p>\n

\"image\"<\/p>\n

<\/p>\n

Choose \"Use MinTTY\". Click Next.<\/p>\n

\"image\"<\/p>\n

<\/p>\n

Choose \"Only ever fast-forward\". Click Next.<\/p>\n

\"image\"<\/p>\n

<\/p>\n

Choose if you'd like to use the Credential Manager. I'm only connecting VSCode with GitHub, so I don't need it. You can always reinstall to add features if you find out that you do need it later. Click Next.<\/p>\n

<\/p>\n

\"image\"<\/p>\n

<\/p>\n

Check both boxes. Click Next.<\/p>\n

<\/p>\n

\"image\"<\/p>\n

<\/p>\n

Uncheck both boxes. Click Install.<\/p>\n

\"image\"<\/p>\n

<\/p>\n

You're all done! You don't need to launch Git or view the release notes unless you want to. Click Finish.<\/p>\n

\"image\"<\/p>\n

<\/p>\n

Git is installed!<\/p>\n

<\/p>\n\n<\/div>","rendered":"

\n

Lecture: Installing Git on MacOS<\/a><\/p>\n

Lecture: Configuring VSCode with Git<\/a><\/p>\n

\n

Download Git<\/a> – Visit this website to download Git for your operating system.<\/p>\n

\n

Choose your operating system and download the latest stable release.<\/p>\n

\"image\"<\/p>\n

\n

<\/a>Downloading Git for MacOS<\/h3>\n

Click on macOS. It should take you to a page with instructions for installing Git.<\/p>\n

\"image\"<\/p>\n

\n

Open a terminal by pressing “Command + Space” and type “terminal”. Choose the application named Terminal.<\/p>\n

\"image\"<\/p>\n

\n

If you don’t already have it, install Homebrew by copying the line of code on the Homebrew site<\/a>. Paste it into the terminal and press enter. If you don’t know if you have it or not, try installing Git and if it fails, install Homebrew.<\/p>\n

\n

\"image\"<\/p>\n

\n

Don’t forget to run the commands given by Next Steps after Homebrew is installed.<\/p>\n

\"image\"<\/strong><\/p>\n

\n

Install Git by running brew install git<\/p>\n

\"image\"<\/p>\n

\n

Run git on the command line to ensure it was installed successfully.<\/p>\n

To run git, type git and press enter.<\/p>\n

\"image\"<\/p>\n

\n

If git runs, you’re done! If not, make sure you installed Homebrew correctly, including adding brew to your PATH.<\/p>\n

<\/a>Downloading Git for Windows<\/h3>\n

After the installer downloads, run the installer. Click Next.<\/p>\n

\"image\"<\/p>\n

\n

The default path is fine. Click Next.<\/p>\n

\"image\"<\/p>\n

\n

If you want a Desktop Icon, check the box next to “On the Desktop”. You won’t really need to run the Git GUI, so you probably won’t directly run this program. You likely won’t need the icon, but that’s up to you.<\/p>\n

\n

If you want to be able to right click and see “Open Git Bash” or “Open Git GUI” from the file explorer, check the boxes next to<\/p>\n

Windows Explorer integration<\/p>\n

Open Git Bash here<\/p>\n

Open Git GUI here<\/p>\n

\n

Make sure to check the boxes next to<\/p>\n

Git LFS<\/p>\n

Associate .Git* configuration files with the default text editor<\/p>\n

Associate .sh files to be run with Bash<\/p>\n

Add a Git Bash Profile to Windows Terminal<\/p>\n

\n

Uncheck the box next to<\/p>\n

Scalar (Git add-on to manage large-scale repositories)<\/p>\n

\n

Click Next.<\/p>\n

\"image\"<\/p>\n

\"image\"<\/p>\n

\n

\n

Choose what you want to name the shortcuts in your Start Menu or click “Don’t create a Start Menu folder” if you don’t want the shortcut. Click Next.<\/p>\n

\"image\"<\/p>\n

\n

Choose “Visual Studio Code as Git’s default editor”. Click Next.<\/p>\n

\"image\"<\/p>\n

\n

Either of these options is fine. Traditionally, your main branch on Git is named the “master branch”. Branches are how you test out features; you switch branches to make a copy of the code to toy around with features without breaking the main build. When your feature is ready, you merge it back onto the “master branch”. However, recently, this has come up as perhaps inappropriate, and so Git is working to rename it.<\/p>\n

\n

If you want to rename your main branch now, choose the second option. If you want to leave it until Git officially renames it, choose the first option. Either option is fine.<\/p>\n

\n

Click Next.<\/p>\n

\"image\"<\/p>\n

\n

Choose “Git from the command line and also from 3rd-party software”. You need to check this so that VS Code can access Git.<\/p>\n

\"image\"<\/p>\n

\n

Choose “Use bundled OpenSSH”. Click Next.<\/p>\n

\n

\"image\"<\/p>\n

\n

Choose “Use the OpenSSL library”. Click Next.<\/p>\n

\"image\"<\/p>\n

\n

Choose “Checkout as-is, commit Unix-style line endings”. This helps preserve formatting when getting code to and from GitHub. Click Next.<\/p>\n

\"image\"<\/p>\n

\n

Choose “Use MinTTY”. Click Next.<\/p>\n

\"image\"<\/p>\n

\n

Choose “Only ever fast-forward”. Click Next.<\/p>\n

\"image\"<\/p>\n

\n

Choose if you’d like to use the Credential Manager. I’m only connecting VSCode with GitHub, so I don’t need it. You can always reinstall to add features if you find out that you do need it later. Click Next.<\/p>\n

\n

\"image\"<\/p>\n

\n

Check both boxes. Click Next.<\/p>\n

\n

\"image\"<\/p>\n

\n

Uncheck both boxes. Click Install.<\/p>\n

\"image\"<\/p>\n

\n

You’re all done! You don’t need to launch Git or view the release notes unless you want to. Click Finish.<\/p>\n

\"image\"<\/p>\n

\n

Git is installed!<\/p>\n

\n<\/div>\n","protected":false},"author":1,"menu_order":5,"template":"","meta":{"pb_show_title":"","pb_short_title":"","pb_subtitle":"","pb_authors":[],"pb_section_license":""},"chapter-type":[49],"contributor":[],"license":[],"class_list":["post-69","chapter","type-chapter","status-publish","hentry","chapter-type-numberless"],"part":18,"_links":{"self":[{"href":"https:\/\/libraryresources.nse.org.ng\/computersciencetwo\/wp-json\/pressbooks\/v2\/chapters\/69","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/libraryresources.nse.org.ng\/computersciencetwo\/wp-json\/pressbooks\/v2\/chapters"}],"about":[{"href":"https:\/\/libraryresources.nse.org.ng\/computersciencetwo\/wp-json\/wp\/v2\/types\/chapter"}],"author":[{"embeddable":true,"href":"https:\/\/libraryresources.nse.org.ng\/computersciencetwo\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":1,"href":"https:\/\/libraryresources.nse.org.ng\/computersciencetwo\/wp-json\/pressbooks\/v2\/chapters\/69\/revisions"}],"predecessor-version":[{"id":70,"href":"https:\/\/libraryresources.nse.org.ng\/computersciencetwo\/wp-json\/pressbooks\/v2\/chapters\/69\/revisions\/70"}],"part":[{"href":"https:\/\/libraryresources.nse.org.ng\/computersciencetwo\/wp-json\/pressbooks\/v2\/parts\/18"}],"metadata":[{"href":"https:\/\/libraryresources.nse.org.ng\/computersciencetwo\/wp-json\/pressbooks\/v2\/chapters\/69\/metadata\/"}],"wp:attachment":[{"href":"https:\/\/libraryresources.nse.org.ng\/computersciencetwo\/wp-json\/wp\/v2\/media?parent=69"}],"wp:term":[{"taxonomy":"chapter-type","embeddable":true,"href":"https:\/\/libraryresources.nse.org.ng\/computersciencetwo\/wp-json\/pressbooks\/v2\/chapter-type?post=69"},{"taxonomy":"contributor","embeddable":true,"href":"https:\/\/libraryresources.nse.org.ng\/computersciencetwo\/wp-json\/wp\/v2\/contributor?post=69"},{"taxonomy":"license","embeddable":true,"href":"https:\/\/libraryresources.nse.org.ng\/computersciencetwo\/wp-json\/wp\/v2\/license?post=69"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}