You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: en/pe-docs/docs/infrastructure/credentials/set-up-git-provider-authentication-for-choreo-deployments.md
+15-15Lines changed: 15 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,13 +22,13 @@ You can connect Bitbucket, GitLab, Azure DevOps repositories to Choreo organizat
22
22
23
23
Authorizing Choreo as a GitHub application grants Choreo the following permissions to perform the respective actions on your behalf within the repository:
|Issues | Y | N | Read component ID label to filter the pull requests|
28
+
|Metadata | Y | N | List repositories|
29
+
|Contents | Y | Y | List branches and create a branch to commit sample code|
30
+
|Pull Request | Y | Y | Create a pull request if you start with a Choreo sample|
31
+
|Webhooks | Y | Y | Trigger automatic deployment and configuration generation|
32
32
33
33
## Authorize Bitbucket with Choreo
34
34
@@ -46,16 +46,16 @@ Authorizing using an API token from Bitbucket grants Choreo the following permis
46
46
47
47
Authorizing using a personal access token (PAT) obtained from your GitLab self-managed server grants Choreo the following permissions to perform the respective actions on your behalf within the repository.
|API | Grants full read/write access to the API, covering all groups and projects, as well as read/write access to the repository.|
52
52
53
53
## Authorize Azure DevOps with Choreo
54
54
55
55
Authorizing Choreo using a Personal Access Token (PAT) from Azure DevOps grants Choreo the following permissions to perform actions on your behalf within the selected organization and project.
0 commit comments