The short answer
Review files, history and collaborator access before sharing.
Try it in three steps
- Learn settings with a non-sensitive practice repository.
- List collaborators and necessary permissions.
- Inspect history, attachments and automation outputs for secrets.
A practice prompt
Before you start
Focus here on visibility; credential storage is covered separately.
Practice material (fictional)
Repository A is public. B is private with two approved collaborators. A third person receives B's URL without access being granted.Replace placeholders in the prompt with this material, or append the material if there are no placeholders. Reading time excludes doing the exercise.
Review the fictional repository visibility, collaborators and sharing path. Explain sharing a link versus granting access without changing visibility.What to look for (not a recorded test result)
A is public; sharing B's URL does not grant access. Do not make B public just for convenience; review history and attachments too.
If it goes wrong
A credential committed historically requires exposure handling even if removed in a later commit.
Check your result
Sharing scope is clear and private material is kept out of the code-sharing process.
References and scope
The links below support the concepts or product navigation. The steps and exercises are our teaching suggestions, not official certification or measured customer outcomes. Product interfaces and availability may change. References checked on 2026-10-17.