Quick Links to Your Git Repository

Updated 9 months ago by Copado Solutions

Copado provides quick links to your Git branches, commits, tags and pull requests in order to see relevant information in your Git repository provider's end.

The quick links View in Git or Pull Request can be found in the records of the following objects:

  • Git Snapshot (for branch).
  • Snapshot Commit (for commits).
  • User Story (for the feature branch if you are using Copado's Git flow).
  • User Story Commit (for commits).
  • Promotion (in the Deployments related list).

How to Use It

  1. Go to your Git Repository record.
  2. Select a Git provider from the options in the drop-down menu (GitHub, Bitbucket, Gitlab, Microsoft Team Service or Others).
    1. Choose the Others option if you are working with Bitbucket Server or any other Git service provider that is not listed in the menu.
    2. If you are using Azure, select Microsoft Team Service.
  3. Fill in the Branch Base URL, Commit Base URL, Pull Request Base URL, and Tag Base URL:
    • Branch Base URL examples:
      • https://github.com/{companyName}/{repositoryName}/tree/
      • https://bitbucket.org/{companyName}/{repositoryName}/branch/
      • https://gitlab.com/{companyName}/{repositoryName}/tree/
      • https://{companyName}.visualstudio.com/_git/{projectName}/tree/
      • https://dev.azure.com/{organizationName}/{projectName}/_git/{repositoryName}?version=GB
    • Commit Base URL examples:
      • https://github.com/{companyName}/{repositoryName}/commits/
      • https://bitbucket.org/{companyName}/{repositoryName}/commits/
      • https://gitlab.com/{companyName}/{repositoryName}/commit/
      • https://{companyName}.visualstudio.com/_git/{projectName}
      • https://dev.azure.com/{organizationName}/{projectName}/_git/{repositoryName}/commit/
    • Pull Request Base URL examples:
      • https://github.com/{companyName}/{repositoryName}/
      • https://bitbucket.org/{companyName}/{repositoryName}/
      • https://gitlab.com/{companyName}/{repositoryName}/
      • https://{companyName}.visualstudio.com/_git/{projectName}/
      • https://dev.azure.com/{organizationName}/{projectName}/_git/{repositoryName}/
    • Tag Base URL examples:
      • https://github.com/{companyName}/{repositoryName}/tags/
      • https://bitbucket.org/{companyName}/{repositoryName}/src/
      • https://gitlab.com/{companyName}/{repositoryName}/tags/
      • https://{companyName}.visualstudio.com/_git/{projectName}/tags/
      • https://dev.azure.com/{organizationName}/{projectName}/_git/{repositoryName}/tags

    The example below shows the Git link setup for GithHub provider:
  4. Save the Git Repository record.
  5. Navigate to one of your Git snapshots and find the View in Git field with the name of the branch. This link redirects to the branch page in the Git repository:
  6. Navigate to one of the commits in your Git Snapshot record and find the View in Git field with the id of the commit. This link redirects to the corresponding commit page in the Git repository:
  7. The User Story Commits record also has a View in Git field that is conveniently located in the User Story Commits related list in the User Story layout:
  8. The Pull Requests button on any User Story that has commits allows you to see how the changes of an individual user story will affect the destination org when deployed.
    If you click on this button, you will be redirected to the pull request page in your Git repository. The pull request is populated with the user story's feature branch and the destination branch linked to the destination environment, as defined in the deployment flow:
  9. A Pull Requests link appears in any deployment located in the Deployments related list of a Promotion record in order to see how the deployment of the promotion will affect the metadata in the destination org.
    If you click on this link, you will be redirected to the pull request page in your Git repository. The pull request is populated with the promotion branch and the destination branch linked to the destination environment of the Promotion:

How did we do?