changes¶
vb changes [OPTIONS] [PATHS ...]
Description¶
Report the change status of files in the current check-out. If one or more PATHS are specified, only changes among the named files and directories are reported. Directories are searched recursively.
Each line of output is the name of a changed file, with paths shown
according to the relative-paths setting, unless overridden by the
--abs-paths or --rel-paths options.
By default, all changed files are selected for display. This behavior
can be overridden by using one or more filter options (listed below),
in which case only files with the specified change type(s) are shown.
As a special case, the --no-merge option does not inhibit this default.
This default shows exactly the set of changes that would be checked-in
by the commit command.
If no filter options are used, or if the --merge option is used, the
artifact hash of each merge contributor check-in version is displayed at
the end of the report. The --no-merge option is useful to display the
default set of changed files without the merge contributors.
If change type classification is enabled, each output line starts with
a code describing the file’s change type, e.g. EDITED or RENAMED. It
is enabled by default unless exactly one change type is selected. For
the purposes of determining the default, --changed counts as selecting
one change type. The default can be overridden by the --classify or
--no-classify options.
--edited and --updated produce disjoint sets. --updated shows a file
only when it is identical to that of its merge contributor, and the
change type classification is UPDATED_BY_MERGE or UPDATED_BY_INTEGRATE.
If the file had to be merged with any other changes, it is considered
to be merged or conflicted and therefore will be shown by --edited, not
--updated, with types EDITED or CONFLICT. The --changed option can be
used to display the union of --edited and --updated.
--differ is so named because it lists all the differences between the
checked-out version and the check-out directory. In addition to the
default changes (excluding --merge), it lists extra files which (if
ignore-glob is set correctly) may be worth adding. Prior to doing a
commit, it is good practice to check --differ to see not only which
changes would be committed but also if any files should be added.
If both --merge and --no-merge are used, --no-merge has priority. The
same is true of --classify and --no-classify.
The vb changes --extra command is equivalent to vb extras.
Options¶
- --abs-paths¶
Display absolute pathnames
- -b, --brief¶
Show a single keyword for the status
- --rel-paths¶
Display pathnames relative to the current working directory
- --hash¶
Verify file status using hashing rather than relying on file mtimes
- --case-sensitive BOOL¶
Override case-sensitive setting
- --dotfiles¶
Include unmanaged files beginning with a dot
- --ignore <CSG>¶
Ignore unmanaged files matching CSG glob patterns
- --header¶
Identify the repository if report is non-empty
- -v, --verbose¶
Say
(none)if the change report is empty
- --classify¶
Start each line with the file’s change type
- --no-classify¶
Do not print file change types
Filter options¶
- --edited¶
Display edited, merged, and conflicted files
- --updated¶
Display files updated by merge/integrate
- --changed¶
Combination of the above two options
- --missing¶
Display missing files
- --added¶
Display added files
- --deleted¶
Display deleted files
- --renamed¶
Display renamed files
- --conflict¶
Display files having merge conflicts
- --meta¶
Display files with metadata changes
- --unchanged¶
Display unchanged files
- --all¶
Display all managed files, i.e. all of the above
- --extra¶
Display unmanaged files
- --differ¶
Display modified and extra files
- --merge¶
Display merge contributors
- --no-merge¶
Do not display merge contributors
- --no-extra¶
Do not display unmanaged files
Examples¶
Init and open a repository
$ vb init changes_repo.vbyte
project-id: dd6de12bc71fd4ee1b802f18ee846f65eae4f70a
server-id: 0216fc2cb8598309bcd30661b0a360da830b77c5
admin-user: ubuntu (initial remote-access password is "XkSg8AdsCp")
$ vb open -f changes_repo.vbyte
project-name: <unnamed>
repository: /tmp/sphinx_tests/3f8f0ffb/changes_repo/changes_repo.vbyte
local-root: /tmp/sphinx_tests/3f8f0ffb/changes_repo/
config-db: /tmp/sphinx_tests/3f8f0ffb/.visionbyte
project-code: dd6de12bc71fd4ee1b802f18ee846f65eae4f70a
checkout: 15a64a1e10fb3803f89d6475306d5261fd359f5c 2026-03-31 13:00:07 UTC
tags: trunk
comment: initial empty check-in (user: ubuntu)
check-ins: 1
Create and add files to repository
$ vb sys echo "alpha" > alpha.txt
$ vb sys echo "beta" > beta.txt
$ vb sys echo "gamma" > gamma.txt
$ vb sys echo "test of missing" > missing.txt
$ vb add *.txt
ADDED alpha.txt
ADDED beta.txt
ADDED gamma.txt
ADDED missing.txt
Show pending changes after removing the managed file and create an unmanaged file
$ vb sys echo "extra" > extra.txt
$ vb sys rm missing.txt
$ vb changes
ADDED alpha.txt
ADDED beta.txt
EXTRA extra.txt
ADDED gamma.txt
MISSING missing.txt
Show only unmanaged and missing files
$ vb changes --extra --missing
EXTRA extra.txt
MISSING missing.txt