GitHub from the Command Line: A Beginner's Guide Using git and gh

"Using Git on the terminal using the command line is, by far, the preferred way to interact with repos. Why? Transparency: You see exactly what's happening. Speed: Fewer clicks, no mouse gymnastics. Scriptability: Automate repetitive tasks. Portability: Works the same across macOS, Linux, and Windows. Less mess ups: If we're honest, this is actually the main reason -so many people have had bad IDE/Git GUI experiences that many prefer the CLI"

"VSCode is great - but sometimes it obscures what's happening, does things you don't expect, and leads you to sloppy choices. It really pays to know how to do it right. Scenario In this hands-on portion, you're going to create a repo, clone it, make changes locally, and move those changes to the remote. Step 0: Prerequisities You need three prerequisites to do this hands-on tutorial: Step 1: Stay organized Somewhere on your computer, create a github.com directory to organize your GitHub repositories. Inside that directory, create a subdirectory for your GitHub user. mkdir github.comcd github.commkdir your-namecd your-name Clone your own repos and forks to your subdirectory. Create subdirectories for other users and orgs whose repos you clone. For example, if you clone a repo from github.com/YakDriver, create a YakDriver directory inside github.com. Then clone the YakDriver repo inside the YakDriver directory. This keeps your repos tidy and makes it clear at a glance where a repo came from."

Using the Git command line delivers transparency, speed, automation, cross-platform consistency, and fewer GUI-related errors. Organize local repositories by creating a central github.com directory and subdirectories for each user or organization. On GitHub, create a new repository and optionally add a README, license, and .gitignore. Clone repositories into the appropriate local subdirectory with git clone. Make changes locally, commit them, and push to the remote to transfer work. Clear local directory structure and command-line proficiency reduce surprises from IDEs and improve correct, repeatable Git workflows.

Read at Medium