Revisions, locks, checks and conflicts

Revisions

Every successful commit creates a new immutable revision. History shows:

• revision number;
• author;
• date and time;
• commit message;
• changed paths.

Do not put passwords, secrets or personal data in commit messages.

Locks

A lock protects a path from concurrent modification.

• Exact lock — the specific path only;
• Recursive lock — a folder and its descendants.

Before force release, verify the owner and reason. Forced release is audited and requires an explanation.

Validation checks

A repository may require pre-commit checks such as:

• source syntax;
• forbidden paths;
• secret scanning;
• other enabled repository policies.

Possible results are:

• passed;
• warning;
• failed;
• error;
• skipped.

A blocking failure prevents commit.

“Needs update” conflict

This means the server tree is newer than the workspace base revision.

Correct sequence:

1. preserve local work;
2. run Update;
3. resolve any conflicts;
4. review Status and Diff;
5. Commit.

Content conflict

When both local and remote versions changed the same path, choose:

• local;
• remote;
• manual.

For manual resolution, edit carefully, remove conflict markers, verify the result and mark the conflict as resolved.

Read-only repository

A read-only repository can still be viewed and downloaded according to permissions, but commits are blocked. Only an authorized administrator/owner can return it to Active.