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: features/integration-github-bitbucket-gitlab.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ You can log into Private Packagist using an account on GitHub.com, Bitbucket.org
9
9
10
10
You can then either create a new organization directly synchronized with a GitHub organization, Bitbucket workspace or a GitLab group, or you can enable synchronization for an existing Organization in _Settings_.
Apart from synchronizing teams, users, and permissions, setting up the integration will simplify the addition of new packages to your Composer repository. When you create a **new repository** on GitHub, Bitbucket, or GitLab, it will be **added as a Composer package automatically** if it contains a _composer.json_ file. If you’d like to add existing repositories as packages, you can do so with the click of a button on the Packages tab in your organization.
15
15
@@ -20,7 +20,7 @@ Apart from synchronizing teams, users, and permissions, setting up the integrati
20
20
Private Packagist integrates with the following systems:
21
21
22
22
#### GitHub
23
-
* OAuth: Users authenticate on Private Packagist with their GitHub accounts
23
+
* OAuth: Users authenticate on Private Packagist with their GitHub accounts. If you use Private Packagist Self-Hosted, first create a GitHub app by following these [steps](../docs/self-hosted/github-integration-setup.md).
24
24
* Synchronization:
25
25
* Keeps teams, their members, and access permissions in sync with your GitHub organization
26
26
* Code Credentials: GitHub App or GitHub API Token
@@ -41,6 +41,7 @@ Private Packagist integrates with the following systems:
41
41
* Webhooks: Code changes and releases
42
42
43
43
#### Bitbucket Data Center / Server
44
+
44
45
* OAuth: Users authenticate on Private Packagist with their Bitbucket Data Center / Server accounts. Follow [this setup](../docs/cloud/bitbucket-server-integration-setup.md) for Cloud plans or [this setup](../docs/self-hosted/bitbucket-server-integration-setup.md) for Self-Hosted.
45
46
* Synchronization:
46
47
* Keeps users and access permissions in sync with your Bitbucket Server projects
@@ -65,6 +66,7 @@ Private Packagist integrates with the following systems:
65
66
* Webhooks: Code changes and releases
66
67
67
68
#### AWS CodeCommit
69
+
* Code Credentials: Either create HTTPS Git credentials and store it as HTTP Basic credential or grant us access via SSH key
68
70
* Webhook:
69
71
* Users need to [create an AWS CodeCommit Trigger](https://docs.aws.amazon.com/codecommit/latest/userguide/how-to-notify-sns.html) using the generic hook URL from the package page
70
72
* Code changes are available automatically. For releases, you need to select "All repository events" for the events type.
0 commit comments