Glossary · Source control and deployment
Rollback
A controlled way to restore a known prior state after a release causes unacceptable problems.
Also called: revert
Definition
Rollback can mean redeploying a previous artifact, reverting a source change, restoring data, reversing configuration, or routing traffic back. The correct method depends on what the release changed.
Why it matters
A tested rollback path limits customer impact and decision pressure when a production change fails.
Common misunderstanding
Reverting code alone may not reverse a database, DNS, content, credential, or external-system change.
Related terms
Related system family: Hosting & Release
Sources
- Best practices for repositories (opens in a new tab) · GitHub Docs
Last reviewed July 16, 2026