Differences

This shows you the differences between two versions of the page.

--- public:99_annexes:annex-b-terms-and-definitions:g:git [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1
+++ public:99_annexes:annex-b-terms-and-definitions:g:git [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
@@ Line 1: / Line 1: @@
+====== Git ======
+[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
+===== Discussion =====
+Git is a distributed [[public:99_annexes:annex-b-terms-and-definitions:v:version_control_system|Version Control System]] used to record, organize, compare, and exchange changes to files and directories maintained in a repository.
+A Git repository contains identifiable revisions of managed [[public:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifacts]] and preserves relationships among those revisions.
+Git represents recorded repository states as commits. Git workflows commonly use:
+  * Repositories
+  * Commits
+  * Branches
+  * Tags
+  * References
+  * Working trees
+  * Staging
+  * Merging
+  * Rebasing
+  * Fetching
+  * Pulling
+  * Pushing
+  * Cloning
+Git records repository states and the relationships among commits. This history enables users and automated processes to:
+  * Identify changes
+  * Compare repository states
+  * Trace the ancestry of a change
+  * Retrieve an identified repository state
+  * Restore or reuse an identified repository state
+  * Reproduce managed content associated with an identified commit
+Within Crucible documentation, Git provides repository and change-history capabilities used by:
+  * Git-based workflows
+  * GitOps practices
+  * [[public:99_annexes:annex-b-terms-and-definitions:c:ci_cd_pipeline|CI/CD Pipelines]]
+  * Configuration management
+  * Automated build operations
+  * Automated deployment operations
+  * Automated validation operations
+  * [[public:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]]
+  * [[public:99_annexes:annex-b-terms-and-definitions:r:reproducibility|Reproducibility]]
+  * [[public:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]
+===== Definition =====
+//distributed [[public:99_annexes:annex-b-terms-and-definitions:v:version_control_system|Version Control System]] that records identifiable repository states and preserves the relationships among those states//
+===== Source =====
+Adapted from:
+  * Git Project documentation
+  * [[public:99_annexes:annex-b-terms-and-definitions:v:version_control_system|Version Control System]]
+===== Note =====
+The name **Git** is not an acronym and should not be written as **GIT**.
+Git is a type of [[public:99_annexes:annex-b-terms-and-definitions:v:version_control_system|Version Control System]].
+Git is distinct from repository-hosting services such as GitHub, GitLab, and Bitbucket. Those services can host and manage Git repositories, but they are not Git itself.
+Git does not require a single permanent central repository. A project can designate one repository as an authoritative or shared repository through policy and workflow conventions.
+A Git-based workflow uses Git repository states and operations to coordinate change. The existence of a Git repository alone does not define:
+  * The workflow
+  * Approval rules
+  * Branch strategy
+  * Merge strategy
+  * Automation
+  * Build behavior
+  * Deployment behavior
+===== Example =====
+A contributor commits a [[public:99_annexes:annex-b-terms-and-definitions:d:declarative_configuration|Declarative Configuration]] change to a Git branch. A review process approves and merges the change into a designated branch. A [[public:99_annexes:annex-b-terms-and-definitions:c:ci_cd_pipeline|CI/CD Pipeline]] identifies the resulting commit and initiates automated build, validation, and deployment operations associated with that repository state.
+----
+<WRAP centeralign>
+© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
+</WRAP>