wvs project

Shows help messages for all project commands.

Options

  -h, --help   help for project
      --json   Help message for json

wvs project clone

Clone a backend project.

Synopsis

Allows you to clone a project from WVS.io. By default the input parameter is the project id that should be cloned.

* To see list of available project use: 'wvs project clone --list'.
* To clone with an SSH url instead of id, use the --sshUrl option.
wvs project clone <projectID> [flags]

Options

  -h, --help            help for clone
  -l, --list            List my projects
      --sshUrl string   URL for the project

wvs project create

Create new project.

Synopsis

Allows user to create a new project based on a template and then immediately clone it to specified empty directory.

wvs project create [flags]

Options

  -h, --help              help for create
  -l, --list              List available template names and exit.
  -n, --name string       New project's name
  -t, --template string   Template to create the project from

wvs project import

Import current non-wvs project into the wvs backend.

Synopsis

Allows user to import non-empty project in current directory into the WVS backend.

wvs project import [flags]

Options

  -h, --help             help for import
  -n, --name string      Imported project's name
  -v, --variant string   Import template variant

wvs project pull

Pull latest from server.

Synopsis

Allows user to pull all recent changes from the backend.

wvs project pull [flags]

Options

  -h, --help   help for pull

wvs project push

Push finished changelists to server.

Synopsis

Allows user to push all pending changelists to the backend.

wvs project push [flags]

Options

  -h, --help   help for push

wvs project setup

Sets up the repository to be a compliant WVS project.

Synopsis

Examines the current repository and sets all the necessary configuration values so that it is valid WVS project.

All repositories are git repositories and can be used as such with no further configuration. However, some WVS tools and features (e.g. flows, WVS clients, changelist locking, etc) require additional configuration and metadata. All of this metadata is contained in a directory called ‘.wvs’ at the root of the project. The presence of a valid .wvs folder at the root of the project is the only requirement to be considered a ‘WVS project’ as opposed to a plain git repository.

Setting up a plain git repository to be a WVS project does not in any way impact the operation of git or any git compatible tools. It merely enables additional WVS platform feature.

wvs project setup [flags]

Options

  -h, --help   help for setup

wvs project status

Shows the current status of the project.

Synopsis

Displays current information about the project.

wvs project status [flags]

Options

  -h, --help   help for status

See also

  • wvs - A Command Line Interface for interacting with a Wevr Virtual Studio.