趋势解读：Cross-org Dependabot access for internal repositories，解读最新 AI 进展

Dependabot can now access internal repositories hosted in other organizations within your enterprise. Consider the situation where you have a dependency hosted in an internal GitHub repository. This repository is in the same enterprise as the project that uses the dependency, but it’s in a different organization. In this situation, you can now grant Dependabot the ability to access all internal repositories, and you can do this from your enterprise’s Advanced Security Policies page. Previously, Dependabot could only access repositories within the same organization, which meant cross-organization dependencies in internal repositories couldn’t receive automatic updates. With this change, enterprise and organization administrators can grant Dependabot access to all internal repositories across their enterprise, so Dependabot can open pull requests for dependencies regardless of which organization hosts them. For internal and public repositories : Enable Dependabot access permanently at the enterprise level. Once enabled, all current and future internal repositories will automatically have Dependabot access. This improvement is available today on github.com and will come to enterprise server in GHES 3.22. To enable Dependabot for all internal repositories in your organization: Navigate to your enterprise’s “Policies” page. Select Advanced Security from the left-side pane. Scroll to the end of the page to the “Grant Dependabot access to repositories” section. Select the policy for repositories you’d like to use for updates with Dependabot. Public, private, and internal repository types Have feedback about this feature? We’d love to hear from you in GitHub Community Discussions .