The repository rejects your push. The terminal shows: abort: restricted access. Mercurial is telling you the code cannot go in.
Mercurial Restricted Access is a control mechanism in environments where every commit matters. It enforces permissions at the repository level, blocking writes from users or systems without explicit authorization. This can be tied to branch-level rules, group policies, or integration hooks that run before any changes reach the central source of truth.
The system is built to stop unauthorized changes from polluting critical production code. It works by checking user credentials against an access file or an external authentication service. If the check fails, Mercurial halts the operation. Many teams link this to continuous integration pipelines, ensuring that only reviewed and approved changes enter protected branches.
Restricted access can be configured through hgrc files, repository-level ACLs, or by hooking into Mercurial’s extension framework. Common setups use the acl extension, where you define patterns for branches and user lists. For example, you can allow pushes to default only from a specific group, or block entire namespaces from non-admin accounts. The extension runs server-side, preventing local bypass.
In locked-down systems, these controls are part of compliance frameworks. They secure proprietary code and regulate release workflows. They also reduce risk of merge conflicts that can break deploy pipelines.
For organizations with multiple repositories and distributed teams, Mercurial restricted access is not just security—it’s operational discipline. It ensures that repository history stays clean and predictable.
Want to see restricted access enforced and automated without complex setup? Visit hoop.dev and see it live in minutes.