[ SELECTED SCHOOL KNOWLEDGE ]
GitHub connector
Use GitHub as a source only when the school has enabled and scoped the connector.
A useful starting point
Begin with approved code examples and project documentation. Choose one collection that has a named audience and owner.
Preserve source access
Limit Nexus to approved GitHub spaces. Test with each intended school role and remove access at the source when a user no longer needs it.
Check the connection
Review sync health, citations, deleted material, and permission changes. GitHub availability depends on the school deployment.
Where GitHub can fit
Start with a teaching repository containing approved code examples and project documentation. The value is giving an authorized user a way to find and inspect an answer in material the school already maintains. Choose the audience and owner before enabling the connection.
Define the collection boundary
Exclude repository secrets, private issues, and unrelated staff projects unless a separate, explicit access decision permits the intended use. A source account with broad permissions should not become a reason to expose all of its data to every learner.
Verify the connection
After setup and indexing, search for a function or README example that a student is expected to explain. Open the returned source, check its version, and repeat the search from the intended user account. Then test an account that should not have access.
- Authorize only the required source access.
- Confirm the selected collection and indexing status.
- Test relevance, source links, and permissions.
- Assign an owner for credential renewal and source changes.
Availability and configuration
This page describes the GitHub connection as a school setup option. Availability, authentication, and supported content depend on the deployment and source service. Confirm the actual setup with Nexus before planning a rollout around it.