avo

Initialize a workspace in the current directory

$ avo init

$ avo login

$ avo checkout [branch_name]

$ avo pull

$ avo status

$ avo conflict

$ avo edit

$ avo [subcommand] --help

avo [GLOBAL_OPTIONS] SUBCOMMAND [SUBCOMMAND_OPTIONS] [ARGUMENTS]

--log-to PATH
    Directs log messages from the underlying avocado command to a specified file path. This is a global option for avocado.

--verbose, -v
    Displays detailed execution information from the avocado command. A global option for increased verbosity.

--debug, -d
    Enables debugging output for deeper introspection of the avocado framework's operations. This is a global option.

--help, -h
    Shows the main help message for avocado, or if followed by a subcommand, the help for that specific subcommand.

--version
    Prints the version of the Avocado framework that avo is invoking.

avo is a convenience script provided by the Avocado Test Framework, acting as a direct shortcut to the avocado command. It allows users to invoke any avocado subcommand (e.g., avocado run, avocado list, avocado plugins) by simply typing avo followed by the desired subcommand and its arguments. This provides a quicker way to interact with the framework without having to type 'avocado' repeatedly.

Functionally, avo behaves identically to avocado, passing all arguments directly to the main avocado executable. It's particularly useful for frequent users and scripting, streamlining the execution of test cases, managing plugins, or querying framework information. The underlying avocado framework is a comprehensive, open-source testing solution designed for robust automation of test suites, commonly used in Linux system validation.

avo is not a standalone utility but a simple wrapper script for the avocado test framework. Its existence and behavior are entirely dependent on the installation and functionality of the avocado command. All command-line parsing and option handling are performed by avocado itself, not by avo. Therefore, any errors or unexpected behavior encountered when using avo typically originate from the underlying avocado command.

Users seeking comprehensive documentation on specific options and subcommands should refer to the official avocado documentation and its man page (man avocado).

avo serves purely as a typing shortcut. It is functionally identical to invoking avocado directly. This is a common pattern in command-line interfaces to improve user experience for frequent users by minimizing keystrokes.

avo becomes available automatically when the avocado test framework is installed on a system. It is typically part of the framework's executable scripts and is not a separate package that needs to be installed independently.

The avo script was introduced as a convenience alias within the avocado-framework project. Its primary purpose is to simplify command-line interaction for users frequently using avocado by reducing typing and providing a shorter, more memorable entry point. It reflects a common practice in command-line tool design where a concise alias is provided for a longer, more descriptive command name. Its development is tied directly to the evolution and adoption of the avocado test framework itself, which gained prominence in Linux system validation and open-source testing communities.

avocado(1), python(1)