The providers
A provider that cannot be connected is still listed on purpose. Hiding it would make the page quiet about where this is going, and offering it would make the page claim something it does not do.
GitHub
The row’s action is Connect, or Add account once an account is already connected. It goes to the App’s install page on GitHub. Each connected installation is listed under the row with its account name, its type, and how many repositories this workspace has linked through it. Once an account is connected, open Code, press Connect repository, pick the account, and choose repositories. The App reacts to three events. Installing it and changing which repositories it can see keep the account’s list current. A push to a repository’s default branch re-syncs the Repository source that reads it. Every other event, pull requests included, is acknowledged and ignored.Setting the App up on a self-hosted server
The server needs four variables:GITHUB_APP_ID, GITHUB_APP_PRIVATE_KEY, GITHUB_APP_WEBHOOK_SECRET and GITHUB_APP_SLUG. Without them the server still boots, and its GitHub routes answer 503 naming what is missing. On the App’s own settings page, point the webhook URL at /api/github/webhook and the setup URL at /api/github/setup. See Installation.
Local folders
In local mode the row lists each connected folder with its path, and its action opens the connect dialog on Code.Next steps
Repositories
Connecting a repository and its console.
Enterprise edition
What the enterprise edition adds.