Bridge for Git Explorer
Bridge for Git Explorer enables you to work with work-environment Git-Endevor mappings that are synchronized with Endevor using Endevor Bridge for Git. When you work with a work-environment mapping, you may need to add elements from up the Endevor map back to your mapping. Bridge for Git Explorer reads the information about the mapping that you cloned in your VS Code workspace and provides a list of elements from up the map for a specified Endevor inventory location.
The extension includes the following features:
Table of Contents
Ensure that you meet the following host-side and client-side software requirements before you use Bridge for Git Explorer:
Ensure that you have a Git-Endevor mapping in your VS Code workspace to start working with the extension. Review the use cases to see how you can use the full potential of Bridge for Git Explorer.
With the 0.4.0 release, Bridge for Git Explorer introduces the following benefits:
The extension continually supports Zowe V1 profiles and team configuration files that contain your Endevor Connection details and Bridge for Git server credentials. However, you do not need to have these types of profiles to work with the extension. If you do not have Zowe V1 profiles or team configuration files, the extension prompts you to specify missing values. In this scenario, the specified values are stored till the end of the VS Code session only.
Note: Credentials from existing Zowe V1 and team configuration files persist between Bridge for Git Explorer sessions.
Work with Elements
Expand your Endevor inventory in the tree and proceed to work with the elements.
Follow these steps:
Team Configuration File
Bridge for Git Explorer supports reading a global team configuration (team config) file. Usually, a system administrator or team leader generates a team config file that contains information about the profiles you need to access certain services, such as Endevor and Bridge for Git. You can use global team configs with your team members to share information about your Endevor connections and Bridge for Git server. For more information about team config, see Using Team Profiles on Zowe Docs.
As an application developer, you can obtain a shared global configuration file from your system administrator and use the file to access shared systems. As a system administrator, you need to have Zowe CLI on your workstation before you create a team configuration file.
Review the following use cases to familiarize yourself with the available features of the extension:
Add to Mapping
When you navigate the Endevor map and find the needed element, you can select and add the element to your synchronized mapping. Then you can download the element to your local branch by pulling the element from you remote repository.
Add to Mapping with Dependencies
You can select and add an element with associated files to your synchronized mapping.
Note: An element can have only up to 50 dependencies.
Right-click an element with dependencies you want to add and select Add to Mapping With Dependencies.
As well as with the previous option, you can download an element to your cloned repository by pulling the element, using the in-built git VS Code Pull option or by issuing the
For more information about work-environment Git-Endevor mappings, see Work with Synchronized Repositories.
Review the history of the elements from up the map in your mapping to identify changes and see the authors and dates of changes. The history of changes is displayed in the Element History section in the explorer tree.
Specify Processor Groups for Elements
Specify a processor group for an element.
Review Mapping Activity
The extension enables you to review the Bridge for Git mapping activity that lists events and their respective actions for the currently opened mapping. The events include mapping initialization, refresh, generate, and deletion.
For example, you can review whether a newly added element is already in your mapping so that you can pull the added element back to your local repository.
To identify issues in Bridge for Git Explorer, view specific information related to an error message in the output stream of the extension.
Follow these steps:
Technical Assistance and Support
The Bridge for Git Explorer extension is made available to customers on the Visual Studio Code Marketplace in accordance with the terms and conditions contained in the provided End-User License Agreement (EULA).
If you are on active support for Endevor, you get technical assistance and support in accordance with the terms, guidelines, details, and parameters that are located within the Broadcom Working with Support guide.
This support generally includes:
Technical support cases must be submitted to Broadcom in accordance with guidance provided in “Working with Support”.
Note: To receive technical assistance and support, you must remain compliant with “Working with Support”, be current on all applicable licensing and maintenance requirements, and maintain an environment in which all computer hardware, operating systems, and third party software associated with the affected Broadcom software are on the releases and version levels from the manufacturer that Broadcom designates as compatible with the software. Changes you elect to make to your operating environment could detrimentally affect the performance of Broadcom software and Broadcom shall not be responsible for these effects or any resulting degradation in performance of the Broadcom software. Severity 1 cases must be opened via telephone and elevations of lower severity incidents to Severity 1 status must be requested via telephone.
Copyright © 2023 Broadcom. The term "Broadcom" refers to Broadcom Inc. and/or its subsidiaries.