Phases
Contents
1. Introduction
The phase concept improves safety of history rewriting and control over changesets exchanged (read more). This phase concept aims to "just works" in a transparent manner for any user (read more). It is part of Core and always enabled in any new client but doesn't prevent older client to work on a repository (read more). Advanced user may decide handle phase manually (read more).
This concept is introduced in Mercurial 2.1.
2. Available Phases
- Prevent accidental rewritting part of the history expected to be immutable.
- Keep immature changeset to be exchanged by mistake.
These phases share a hierarchy of traits:
|
immutable |
shared |
public |
x |
x |
draft |
|
x |
secret |
|
|
3. Phase Movements
4. command line interface
4.1. core command
4.2. impact on extension
5. Publishing Repository
6. Upgrade Notes
(If you were looking to the developer oriented page: PhaseDevel)