Gated commit

Uses your system voice; voice and rate in settings.

Snapshot

≈ 3 min read

Names in other languages

No names in other languages are held for this entry yet.

Article bodies are English and are not machine-translated. A name in another language is not a translation of the article.

A gated commit, gated check-in or pre-tested commit is a software integration pattern that reduces the chances for breaking a build (and often its associated tests) by committing changes into the main branch of version control. This pattern can be supported by a continuous integration (CI) server.

To perform a gated commit the software developer must request a gated commit from the CI server before committing the actual changes to a central location. The CI server merges the local changes with the head of the master branch and performs the validations (build and tests) that make up the gate.

So the developer can see if their changes break the build without actually committing the changes. A commit to the central location will only be allowed if the gates are cleared. As an alternative this pattern can be realized using different branches in version control.

For instance, GitHub can force all commits to a branch B to be merge commits from pull requests which have successfully been built on the CI server and are up-to-date (i.e. based or rebased on B).

A gated commit, gated check-in or pre-tested commit is a software integration pattern that reduces the chances for breaking a build (and often its associated tests) by committing changes into the main branch of version control. This pattern can be supported by a continuous integration (CI) server.

To perform a gated commit the software developer must request a gated commit from the CI server before committing the actual changes to a central location. The CI server merges the local changes with the head of the master branch and performs the validations (build and tests) that make up the gate.

So the developer can see if their changes break the build without actually committing the changes. A commit to the central location will only be allowed if the gates are cleared. As an alternative this pattern can be realized using different branches in version control.

For instance, GitHub can force all commits to a branch B to be merge commits from pull requests which have successfully been built on the CI server and are up-to-date (i.e. based or rebased on B).

Text derived from https://en.wikipedia.org/w/index.php?oldid=1319043936 under CC BY-SA 4.0; modifications have been made.

Provenance

snapshot enwiki-001319043936 · captured 1761568229.0 · version history

Cite this page as: encyclopegia.org, “Gated commit”, snapshot enwiki-001319043936. https://encyclopegia.org/a/gated-commit

Sources cited in this revision

4 named source(s) extracted from the cited revision. A source with no author is shown by its publication; nothing is invented.