Skip to content

Commit d2cc6fb

Browse files
Upgrade the integrations page
1 parent 9f01b3b commit d2cc6fb

File tree

3 files changed

+4
-2
lines changed

3 files changed

+4
-2
lines changed
-110 KB
Binary file not shown.
129 KB
Loading

features/integration-github-bitbucket-gitlab.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ You can log into Private Packagist using an account on GitHub.com, Bitbucket.org
99

1010
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_.
1111

12-
![Synchronization](/Resources/public/img/docs/features/Sync-20170306.png)
12+
![Synchronization](/Resources/public/img/docs/features/Sync-20241218.png)
1313

1414
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.
1515

@@ -20,7 +20,7 @@ Apart from synchronizing teams, users, and permissions, setting up the integrati
2020
Private Packagist integrates with the following systems:
2121

2222
#### 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).
2424
* Synchronization:
2525
* Keeps teams, their members, and access permissions in sync with your GitHub organization
2626
* Code Credentials: GitHub App or GitHub API Token
@@ -41,6 +41,7 @@ Private Packagist integrates with the following systems:
4141
* Webhooks: Code changes and releases
4242

4343
#### Bitbucket Data Center / Server
44+
4445
* 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.
4546
* Synchronization:
4647
* Keeps users and access permissions in sync with your Bitbucket Server projects
@@ -65,6 +66,7 @@ Private Packagist integrates with the following systems:
6566
* Webhooks: Code changes and releases
6667

6768
#### AWS CodeCommit
69+
* Code Credentials: Either create HTTPS Git credentials and store it as HTTP Basic credential or grant us access via SSH key
6870
* Webhook:
6971
* 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
7072
* Code changes are available automatically. For releases, you need to select "All repository events" for the events type.

0 commit comments

Comments
 (0)