# Understanding The Git Workflow
My Understanding Of Git Git is a place where one is able to create projects using commands and they can be tried, tested and if something is not right the correction is also done here. Projects worked on via Git are stored in a local repository where GitHub acts as a backup platform for the same therefore , one has to synchronize the project to GitHub. Git allows one to track any changes and/or…
Git represents a platform where projects can be created, tested, and corrected. It operates in the present, requiring each command to be explicitly given for instructions. GitHub serves as a backup for these projects, enabling easy retrieval and public presentation.
Commands in Git are specific instructions that retrieve and relay information based on the command provided. For instance, creating a 'data' subfolder within a local storage folder called 'Kenyan Banks Mortgage Analysis' is done using the command 'mkdir data'. Creating a 'README' file is accomplished with 'touch README.md', and listing the current directory contents is achieved through 'ls'.
Navigating Git involves clear steps where each command represents a particular action. For example, to work on the 'Kenyan Banks Mortgage Analysis' project, one must first open it with Git, move to the 'data' subfolder using 'cd data', and return to the main project directory with 'cd ..'. The command 'git init' initializes a local Git repository within the 'Kenyan Banks Mortgage Analysis' folder.
'ls -la' lists all files, 'git status' confirms changes ready for staging, and 'git add .' stages any changes, if present. 'git status' again confirms readiness to commit the changes. 'git commit -m' adds the change with a descriptive message, and 'git log --oneline' displays all commit history.
GitHub allows projects to be presented publicly and serves as a backup platform. To connect the local and GitHub repositories, one must confirm the current branch name using 'git branch', switch to the 'main' branch if necessary using 'git branch -M main', and then link the local repository to GitHub by copying the SSH key and pasting it after 'git remote add origin'.
Verifying the successful linking is done via 'git remote -v'. Finally, 'git push -u origin main' uploads the local file to GitHub, ensuring it acts as a backup. Despite its complexity, understanding each command's function becomes a formulaic approach rather than relying solely on memorization.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
