When you connect a GitHub repository to Workers Builds or Pages, the accounts and repositories you can pick from are now based on your own GitHub account, so the list reflects the repositories you work with on GitHub. Previously, the list was based on the Cloudflare Workers & Pages GitHub App installations linked to your Cloudflare account, so it could include repositories that you cannot access on GitHub.

The list now shows:
- Your own GitHub account, if the app is installed on it.
- GitHub organizations that have the app installed, where you can access at least one repository.
- The repositories you can access in each of them.
GitHub accounts that belong to other users are no longer listed, even if they have given you access to one of their repositories.
What this means for you:
Authorizing the app and installing it are two separate steps on GitHub. For more details, refer to Install and authorize the app for Workers Builds and Pages.

- If you have already authorized the app with your GitHub user: Nothing changes. You can check on the Authorized GitHub Apps page ↗︎ on GitHub.
- If you have not: The next time you connect a repository, Cloudflare sends you to GitHub to authorize the app. You only need to do this once, even if someone else on your Cloudflare account already connected GitHub.
- If the app is not installed on any GitHub account you can access: After you authorize, install the app on your own GitHub account or an organization, the same as before.
- If an account or organization is missing from the list: Select Add GitHub account and install the app on it.
Projects that are already connected to a repository are not affected and keep building.
For more information, refer to Repository access for Workers Builds and Pages.
Source: Cloudflare


