Affectation de Revue
The process or event of assigning a specific person or group to conduct code review on a pending change or pull request.
View termCategories
Version Control
Browse Version Control terms for IT and DevOps professionals.
Languages
Alias de branche
A secondary name or reference assigned to a branch, often used for flexible environment mapping or backward compatibility in CI/CD pipelines.
View termAmender le commit
A version control operation that modifies the most recent commit, typically to correct or add information before it is pushed.
View termAnnotation de Tag
An optional message attached to a tag in version control, providing metadata such as release notes, version identifiers, or author details to aid in traceability and documentation.
View termAttribution du Blame
A feature in version control systems used to identify which user or commit introduced a particular line of code, aiding in debugging, compliance, and change tracking.
View termAvance Rapide
A type of merge in version control where the current branch pointer is simply moved forward to the target commit, as there are no divergent changes to reconcile.
View termBranche protégée
A branch in a version control repository configured to prevent force pushes, direct commits, or deletion, requiring code review and compliance checks before integration.
View termCheckout du Code
The operation in a version control system that copies files from a repository (or a specific branch or commit) to a local working directory, making them available for editing, testing, or deployment.
View termCherry-Pick
The operation in version control that applies a specific commit from one branch onto another, used for selectively integrating bug fixes or features without merging the entire branch.
View termCommentaire de Ligne
A specific comment attached to a particular line of code in a diff or review interface, enabling precise feedback and annotation during code review.
View termCommentaire de Revue
A note or piece of feedback left by a reviewer on a code change, pull request, or merge request in a version control platform, facilitating collaborative code quality and integration standards.
View termCommit Ancêtre
A previous commit in the history of a branch or repository that forms the basis for subsequent changes, often used for merges and conflict resolution.
View termConflit de fusion
A situation in version control where changes from different branches cannot be automatically reconciled, requiring manual intervention for resolution.
View termDifférence de commit
A view or record showing the exact code changes between commits, used for audit, review, and integration monitoring.
View termExplorateur de Dépôt
A user interface or tool allowing users to navigate, search, and review repository content, structure, and changes across branches and commits.
View termFil de revue
A threaded discussion attached to code review changesets for tracking comments, decisions, and approvals in collaborative workflows.
View termFile d’Attente des Patchs
A series of pending patches or updates managed and applied in order, often used in large-scale code integration and change management systems.
View termFiltre de Tag
A filter mechanism in source control or CI/CD tools allowing users to view, select, or restrict results based on Git tags, typically used for deployment, release, or monitoring operations.
View termFlux de travail de rebase
A sequence in version control where changes from one branch are reapplied onto another, producing a linear history and reducing merge conflicts.
View termFork du dépôt
A personal copy of a repository, allowing contributors to propose changes via pull or merge requests without affecting the source project.
View termFusion Automatique
An automated process that merges code changes into a target branch once all checks, reviews, and conditions are met, minimizing manual intervention.
View termFusion avec écrasement
A Git merging method that condenses all changes from a feature branch into a single commit before integrating into the main branch, streamlining history.
View termFusion d'équipe
The coordinated integration of code contributions from multiple developers or squads into a single branch or repository, often using enterprise workflows or automation.
View termJeton d'accès
A secure, revocable credential generated by systems (e.g., GitHub, GitLab) to authenticate users or services for repository access and API integration.
View termLien d’Issue
The process of establishing connections between issues, tickets, or work items in tracking systems to show dependencies, relationships, or traceability.
View termMarqueur de Conflit
A visual indicator in files generated by version control systems during merge conflicts, marking the boundaries of conflicting code regions that must be resolved before a commit can proceed.
View termMessage de commit
A descriptive summary attached to each commit in version control, documenting the purpose and context of code changes for audit, review, and compliance.
View termMiroir de pull
A synchronization method in which a repository automatically pulls updates from another source, maintaining a mirrored copy for redundancy or distributed integration.
View termMiroir de Pull
A replication mechanism that periodically pulls and synchronizes repository content from an upstream source, ensuring a local or backup copy stays up to date.
View termNettoyage des Tags
The process of removing obsolete, duplicate, or irrelevant Git tags from repositories to maintain clarity in release and deployment tracking.
View termOpération de Clonage
The process of creating a complete local copy of a remote repository, including all branches, tags, and commit history, enabling independent development or integration tasks.
View termOrigine distante
The default remote repository in Git configuration that acts as the main synchronization point for local-to-remote operations.
View termPile de Patchs
A sequential arrangement of dependent patches, managed to be applied, rebased, or merged in order to a codebase, ensuring controlled integration.
View termPolitique de push
A set of rules or permissions defining how, when, and by whom changes may be pushed to repositories; controls integration security and process compliance.
View termProposition de Changement
A formal suggestion for a code or configuration change in a repository, tracked and discussed before being accepted into production or mainline integration.
View termRelecteur de Code
A person or automation designated to examine, comment on, and approve code changes before they are merged, ensuring compliance with policy, standards, and security requirements.
View termRepointage de branche
The operation of changing the base branch pointer in a repository, typically to align with updated integration or release workflows.
View termRevue de patch
A formal review of code modifications bundled as a patch, ensuring quality and compliance before integration or deployment.
View termRécupérer Stash
A Git command that reapplies the most recently stashed changes to the current working directory, removing them from the stash stack.
View termRéécriture de l'historique
The process of altering the commit history in a version control system, typically to clean up, squash, or reorganize commits before merging or publishing changes, often for compliance or readability.
View termScript de hook
A custom script triggered by version control events (e.g., commit, push), automating checks, integrations, or policy enforcement in repositories.
View termStratégie de Pull
The method used by a version control system to retrieve changes from a remote repository, including merge, rebase, and fast-forward techniques, determining how local and remote changes are synchronized.
View termSuivi de Branche
A feature in version control systems that allows a local branch to be associated with a remote branch, enabling seamless synchronization, updates, and monitoring of integration status.
View termSuppression de Branche
The removal of a branch from a repository after it is no longer needed, typically following successful merge or completion of related work.
View termSérie de Patches
A set of related patches grouped and submitted together, typically in open source or enterprise workflows, to address a feature or bugfix in an organized, reviewable manner.
View termTraçabilité des Changements
A documented or automated record showing the lineage and impact of changes, from proposal through approval, merge, and deployment in integration systems.
View termTête détachée
A state in Git where the repository points directly to a commit rather than a branch, often used for review or temporary changes.
View termVisionneuse de diff
A tool or interface within version control platforms that visually displays differences between code changesets or commits.
View termWorkflow de Fork
A collaborative development approach where a developer creates a personal copy (fork) of a repository, makes changes independently, and proposes those changes back to the main project via pull requests, supporting distributed and parallel contributions.
View term