Memory hook: A repository needs instructions as well as code.
Must remember
The README explains purpose and usage. LICENSE states reuse rights. CONTRIBUTING describes contribution expectations. SECURITY directs vulnerability reporting. CODEOWNERS identifies reviewers for matching paths, but required approval depends on protection/ruleset configuration. A code of conduct defines participation expectations and enforcement contacts.
A template repository seeds a new project without preserving the same collaboration relationship/history as a fork. A fork is a related repository used to develop changes independently and propose them upstream. A clone is a local copy of repository history. Choose based on whether the intent is reuse as a new project or continued upstream contribution.
Use branches, directories and focused commits to organize changes. .gitignore excludes matching untracked paths; it does not stop tracking a file already committed. Git LFS stores supported large-file content outside ordinary Git objects with pointers in the repository; it has separate usage considerations.
Repository insights and dependency views help understand activity, contributors and dependencies. Stars bookmark/show interest; watching controls notifications. A high star count is not evidence of security or maintenance quality. Inspect recent activity, documentation, issue handling and license suitability.
Public, private and eligible internal visibility have different audience boundaries. Publishing a repository requires checking its full history and artifacts, not just its current README. Feature previews expose changing functionality; learn the stable capability and verify current availability rather than assuming every account has the same UI.
Choose under exam pressure
| Requirement | Choice and reason |
|---|---|
| Start an independent project from a scaffold | Template repository. |
| Contribute back to an upstream project | Fork plus pull request. |
| Request path-specific review | CODEOWNERS with suitable review enforcement. |
Traps
- A public repository without a license is not automatically freely reusable.
- Adding a tracked file to gitignore does not remove it from history.
Active recall
1. Clone versus fork?
Local repository copy versus a related hosted repository under another owner.
2. What belongs in SECURITY?
How to report vulnerabilities safely and any supported-version policy.
3. Does CODEOWNERS alone require approval?
No; enforcement also depends on configured protections/rulesets.
4. Stars versus watch?
Interest/bookmark versus notification subscription.
5. Why inspect history before publishing?
Old commits may contain confidential data even when current files do not.
Sources
- repositories · creating-and-managing-repositories · about-repositories
- repositories · creating-and-managing-repositories · creating-a-repository-from-a-template
- repositories · managing-your-repositorys-settings-and-features · customizing-your-repository · about-code-owners
- get-started · getting-started-with-git · ignoring-files