## zowe › endevor-bridge-for-git › branch › add

Add a branch to an existing mapping

#### Usage

zowe endevor-bridge-for-git branch add <context> <mapping> <branch> [options]

#### Positional Arguments

- `context` (string)

  - Git-Endevor mapping context (ID of the organization, project, team or owner of the Git repository).

- `mapping` (string)

  - Git-Endevor mapping name (ID of the Git repository).

- `branch` (string)

  - Name of the branch that will be added/removed.

#### Options

- `--endevor-system` | `--endevorsys` | `--system` (string)

  - The Endevor system where your project resides.

- `--endevor-subsystem` | `--endevorsub` | `--sub` | `--subsystem` (string)

  - The Endevor subsystem where your project resides.

- `--system-alias` (string)

  - The alias of Endevor system.

- `--subsystem-alias` (string)

  - The alias of Endevor subsystem.

- `--endevor-environment` | `--endevorenv` | `--env` | `--environment` (string)

  - The Endevor environment where your project resides.

- `--read-only` (boolean)

  - If specified, it is necessary to use the option --endevor-stage-number. The synchronized elements will be read-only.

- `--endevor-stage-number` | `--endevorsn` (string)

  - The Endevor stage where your project resides (only for read only mappings).

- `--mapping-mode` (string)

  - Mapping mode of the mapping ('FULL', 'WORK_ENV_ONLY' or 'MIRROR')

    Allowed values: FULL, WORK_ENV_ONLY, MIRROR

- `--like` (string)

  - Add branch using parameters from another branch in the same repository

- `--repository-check` (string)

  - If set to allowNonEmpty, user can proceed with initialization of the branch even if the branch exists.

    Default value: REQUIRE_EMPTY
    Allowed values: REQUIRE_EMPTY, ALLOW_NON_EMPTY

#### Endevor options (alternatively use an 'endevor' profile)

- `--endevor-protocol` | `--endevorprot` (string)

  - The Endevor SCM Rest API protocol.

    Default value: http

    Allowed values: http, https

- `--endevor-host` | `--endevorh` (string)

  - The Endevor Rest API hostname.

- `--endevor-port` | `--endevorp` (number)

  - The Endevor Rest API port.

- `--endevor-user` | `--endevoru` (string)

  - Mainframe (Endevor) username, which can be the same as your TSO login.

- `--endevor-password` | `--endevorpass` | `--endevorpw` (string)

  - Mainframe (Endevor) password, which can be the same as your TSO password.

- `--endevor-reject-unauthorized` | `--endevorru` (boolean)

  - Reject self-signed certificates.

    Default value: true

- `--endevor-base-path` | `--endevorbp` (string)

  - The Endevor SCM Rest API base path.

    Default value: EndevorService/rest

#### Endevor Bridge for Git connection options (alternatively use an 'ebg' profile)

- `--protocol` | `--prot` (string)

  - The Endevor Bridge for Git SCM protocol.

    Default value: https

    Default value: https
    Allowed values: http, https

- `--host` | `-H` (string)

  - The Endevor Bridge for Git hostname.

- `--port` | `-P` (number)

  - The Endevor Bridge for Git port.

- `--user` | `-u` (string)

  - Endevor Bridge for Git username (your git username).

- `--token` | `-t` (string)

  - Git personal access token (it can be obtained from your Git Enterprise Server).

- `--reject-unauthorized` | `--ru` (boolean)

  - Reject self-signed certificates.

    Default value: false

#### Profile Options

- `--ebg-profile` | `--ebg-p` (string)

  - The name of a (ebg) profile to load for this command execution.

- `--endevor-profile` | `--endevor-p` (string)

  - The name of a (endevor) profile to load for this command execution.

- `--base-profile` | `--base-p` (string)

  - The name of a (base) profile to load for this command execution.

#### Base Connection Options

- `--password` | `--pass` | `--pw` (string)

  - Password to authenticate to service on the mainframe.

- `--token-type` | `--tt` (string)

  - The type of token to get and use for the API. Omit this option to use the default token type, which is provided by 'zowe auth login'.

- `--token-value` | `--tv` (string)

  - The value of the token to pass to the API.

- `--cert-file` (local file path)

  - The file path to a certificate file to use for authentication

- `--cert-key-file` (local file path)

  - The file path to a certificate key file to use for authentication

#### Examples

- Add a branch to my Git-Endevor mapping 'MY-CONTEXT / MY-MAPPING' using the default EBG and Endevor profile:

  - `zowe endevor-bridge-for-git branch add MY-CONTEXT MY-MAPPING MY-BRANCH --endevor-environment ENVNAME --endevor-system SYSNAME --endevor-subsystem SUBNAME`

- Add a branch to my Git-Endevor mapping 'MY-CONTEXT / MY-MAPPING' using the default EBG and Endevor profile by using another branch as a template with different environment:

  - `zowe endevor-bridge-for-git branch add MY-CONTEXT MY-MAPPING MY-BRANCH --like TEMPLATE_BRANCH --endevor-environment DIFFERENT_ENVIRONMENT`

- Add a branch to my Git-Endevor mapping 'MY-CONTEXT / MY-MAPPING' using the default EBG and Endevor profile by using another branch as a template with different system/subsystem:

  - `zowe endevor-bridge-for-git branch add MY-CONTEXT MY-MAPPING MY-BRANCH --like TEMPLATE_BRANCH --endevor-system DIFFERENT_SYSTEM --endevor-subsystem DIFFERENT_SUBSYSTEM`