https://RustRocket.rs -- Cloud Monk Losang Jinpa, Ph.D., MCSE / MCT, https://Rustaceans.rs, Full Stack Cloud Native Rust DevOps Engineer - Rocket Framework Rust Microservices on Kubernetes-AWS-Azure-GCP

Return to GitOps, Git, IaC Glossary, GitHub, Git Glossary, GitHub Glossary, Terraform Glossary, Ansible Glossary, Docker Glossary, Podman Glossary, Containerization Glossary, Kubernetes Glossary, OpenShift Glossary, Rancher Glossary, DevOps Glossary, DevSecOps Glossary, Virtualization Glossary, Cloud Native Glossary, Microservices Glossary, Cloud Computing Glossary, AWS Glossary, Azure Glossary, GCP Glossary, IBM Cloud Glossary, Oracle Cloud Glossary

• Provide a Git glossary of the top 40 Git concepts sorted by the most commonly used. For each concept include a brief description and the URL for the official documentation.

Answer using MediaWiki format.

Creating a Git glossary of the top 40 concepts, prioritized by their commonality of use, involves explaining Git's core functionalities, commands, and workflows that are essential for version control. Git is a distributed version control system that allows multiple developers to work on a project simultaneously, without losing track of their changes. This glossary will cover foundational Git concepts and commands that are frequently used in software development projects.

Given the detail required for 40 concepts, I'll provide an abbreviated list that captures some of the most critical Git concepts in a MediaWiki format. This should serve as a helpful starting point.

This glossary outlines the most commonly used Git concepts, providing a foundation for understanding and utilizing Git for version control in software development projects.

A distributed version control system used to track changes in source code during software development. It allows multiple developers to work on the same project simultaneously.

A digital directory or storage space where your project lives. It can be local to a folder on your computer, or it can be a storage space on GitHub or another online host.

The act of copying an existing Git repository from another location to your local machine. ; Example <source> git clone https://github.com/exampleuser/example-repo.git </source>

A lightweight movable pointer to one of these commits. The default branch name in Git is “master”. ; Example <source> git branch new-feature </source>

An individual change to a file (or set of files). It's like when you save a file, except with Git, every time you save it creates a unique ID. ; Example <source> git commit -m “Add a new feature” </source>

Takes the changes from one branch (in the same repository or from a fork), and applies them into another. This often happens in a pull request. ; Example <source> git merge new-feature </source>

A method of submitting contributions to an open development project. It is initiated by the developer responsible for the project, or by using a GitHub feature.

Adds changes from the remote repository to your local working branch without committing them. ; Example <source> git fetch origin </source>

Fetches and merges changes on the remote server to your working directory. ; Example <source> git pull origin master </source>

Sends committed changes of local branch to a remote repository. ; Example <source> git push origin master </source>

Occurs when Git is unable to automatically resolve differences in code between two commits. ; Example To resolve a merge conflict, edit the files to fix the conflicting changes and then commit the result.

Temporarily shelves (or stashes) changes so you can work on a different branch. ; Example <source> git stash </source>

Reapply commits on top of another base tip. It's used to apply your changes onto another branch. ; Example <source> git rebase master </source>

Marks specific points in history as being important. Typically used for marking release points (v1.0, for instance). ; Example <source> git tag v1.0 </source>

Used to switch between branches or inspect old versions. ; Example <source> git checkout new-feature </source>

Shows the differences between two commits, or between committed and uncommitted changes. ; Example <source> git diff HEAD </source>

Displays committed snapshots. It lets you list the project history. ; Example <source> git log </source>

A common repository that all team members use to exchange their changes. ; Example <source> git remote add origin https://github.com/exampleuser/example-repo.git </source>

A text file that tells Git which files or folders to ignore in a project. ; Example To ignore all “.txt” files, add “

• .txt” to the .gitignore file.

This glossary introduces some of the core concepts and commands used in Git, offering a foundational understanding for managing and contributing to software projects with version control. For a comprehensive exploration of all 40 concepts, extensive documentation and resources on Git are recommended.

This overview provides a snapshot of essential Git concepts and workflows. Expanding your knowledge to include all 40 concepts would involve deeper exploration into Git's documentation, tutorials, and community resources, where you can find detailed explanations, examples, and best practices for using Git effectively in your projects.

Fair Use Sources:

• https://docs.github.com/en/get-started/quickstart/github-glossary
• The Official Git Glossary
• Git Reference
• Git SCM
• B0978TF66B (G4Pg 2021)
• B01NBEQCA1 (PrGt 2016)
• B0827FGT77 (BgGH 2019)
• 9781492091127 (VCgt 2022)
• B07RGKKBTY (GHDum 2019)

• GitHub on DuckDuckGo
• GitHub on GitHub
• GitHub on O'Reilly
• GitHub on Stackoverflow
• GitHub on Reddit
• GitHub on YouTube
• GitHub for Archive Access for Fair Use Preservation, quoting, paraphrasing, excerpting and/or commenting upon