Commit
A recorded project state with metadata and, where applicable, links to earlier states in Git.
Record a selected state
A Git commit records a selected project state with metadata such as a change description and author. Where applicable, it refers to predecessors, forming history. Its content comes from the prepared state; not every working-directory change is automatically included.
In a fictional example, a form correction and its relevant test are recorded together. An unrelated layout change remains outside the selection. This makes the change understandable for later review. A commit confirms neither passing tests nor approval. Saving files, committing, transferring to a shared repository and deployment are separate operations, even when a project connects several automatically.
Sources
Related terms
- Version controlA system that records changes to tracked files and makes earlier states comparable.
- GitA distributed version control system with local repositories and recorded change history.
- BranchA named development line that Git tracks through a movable reference to a commit.
- Code reviewFocused examination of a source change for design, behaviour, clarity and appropriate checks.
- Legacy systemAn existing system still in use, with technical and business dependencies accumulated over time.
- Multi-tenancyMulti-tenancy supports separate customer or group scopes in one solution. A tenant is not automatically one person or one database.
Articles on this topic
Software Development with ASES
Custom software, web and mobile apps