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

Add an element to your Git repository from up the map in Endevor.

#### Usage

zowe endevor-bridge-for-git add element [context] [mapping] [options]

#### Positional Arguments

- `context` (string)

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

- `mapping` (string)

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

#### Options

- `--element-name` | `--name` (string)

  - Name of the Endevor element to add.

- `--element-type` | `--type` (string)

  - Type of Endevor element to add.

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

  - Endevor system where your project resides.

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

  - Endevor subsystem where your project resides.

- `--withDependencies` (boolean)

  - If specified, add the requested element (for example, COBOL copybooks) with dependencies.

    Default value: false

- `--force-get-dependencies` | `--force` (boolean)

  - If specified, bypass the maximum number of dependencies. This only applies to the repository administrator.

    Default value: false

- `--branchId` (string)

  - If specified, add the requested elements to the selected branch.

- `--all-branches` (boolean)

  - If specified, add the requested elements to all synchronized branches in your repository.

    Default value: false

- `--file` | `--fn` (local file path)

  - If specified, read the elements to add from file.
    Ensure that the file is in the format specified in the documentation and follows the example:
    [
    {
    "fullElmName": "ELMNAME",
    "typeName": "ELMTYPE"
    }
    ]

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

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

  - Endevor SCM Rest API protocol.

    Default: http

    Allowed values: http, https

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

  - Endevor Rest API hostname.

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

  - Endevor Rest API port.

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

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

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

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

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

  - Reject self-signed certificates.

    Default: true

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

  - The Endevor SCM Rest API base path.

    Default: EndevorService/rest

#### Endevor Bridge for Git connection options (you can also use an 'ebg' profile)

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

  - Endevor Bridge for Git SCM protocol.

    Default: https

    Default value: https
    Allowed values: http, https

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

  - Endevor Bridge for Git hostname.

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

  - Endevor Bridge for Git port.

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

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

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

  - Git personal access token (Obtain the token from your Git Enterprise Server).

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

  - Reject self-signed certificates.

    Default: false

- `--ebg-base-path` (string)

  - The Endevor Bridge for Git Rest API base path.

#### 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.

    Note: The CLI does not support certificate files that require a password. For more information, search Troubleshooting PEM Certificates in Zowe Docs.

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

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

#### Examples

- Add an element 'MY-ELEMENT-TYPE / MY-ELEMENT-NAME' for your mapping 'MY-CONTEXT / MY-MAPPING':

  - `zowe endevor-bridge-for-git add element MY-CONTEXT MY-MAPPING --name MY-ELEMENT-NAME --type MY-ELEMENT-TYPE`

- Add multiple elements for your mapping 'MY-CONTEXT / MY-MAPPING' from file:

  - `zowe endevor-bridge-for-git add element MY-CONTEXT MY-MAPPING --file MY-FILEPATH.json`