product-example 1 linked patterns checked
GitHub Docs: Deleting a repository
Documents a destructive repository deletion flow that requires users to read warnings, acknowledge effects, type the repository name to verify the target, and then delete the repository.
Read with a purpose
What this source can teach
Use this source to inspect a concrete implementation and the decisions visible in its context.
- Start with the original. Open the source and find the guidance or example relevant to your task.
- Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
- Check the setting. Compare the source's platform, people, and constraints with your own decision.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Typed confirmation | Choose typed confirmation when exact target reproduction materially lowers the risk of deleting or resetting the wrong object. | The required phrase is visible in the same confirmation surface as the input field. | GitHub repository deletion requires typing the repository name to verify the target after warning acknowledgement. |
Comparisons supported by this source
- Typed confirmation vs destructive action confirmation vs confirmation dialog vs password input
GitHub repository deletion requires warning acknowledgement and typing the repository name to verify the target.
Evidence Role
This source is treated as product-example evidence. Its value comes from the specific claims and setting described above.
Publisher: GitHub. Last checked: .