hg-remove - Man Page

• Remove files or directories from the staging area: hg remove path/to/file
• Remove all staged files matching a specified pattern: hg remove --include pattern
• Remove all staged files, excluding those that match a specified pattern: hg remove --exclude pattern
• Recursively remove sub-repositories: hg remove --subrepos
• Remove files from the repository that have been physically removed: hg remove --after

tldr.sh

hg remove [OPTION]... FILE...

Schedule the indicated files for removal from the current branch.

This command schedules the files to be removed at the next commit. To undo a remove before that, see hg revert. To undo added files, see hg forget.

-A/--after can be used to remove only files that have already been deleted, -f/--force can be used to force deletion, and -Af can be used to remove files from the next revision without deleting them from the working directory.

The following table details the behavior of remove for different file states (columns) and option combinations (rows). The file states are Added [A], Clean [C], Modified [M] and Missing [!] (as reported by hg status). The actions are Warn, Remove (from branch) and Delete (from disk):

Note

hg remove never deletes files in Added [A] state from the working directory, not even if --force is specified.

Returns 0 on success, 1 if any warnings encountered.

-A,  --after

record delete for missing files

-f,  --force

forget added files, delete modified files

-S,  --subrepos

recurse into subrepositories

-I,--include <PATTERN[+]>

include names matching the given patterns

-X,--exclude <PATTERN[+]>

exclude names matching the given patterns

-n,  --dry-run

do not perform actions, just print output

[+] marked option can be specified multiple times

rm