Document: LESSONS-001Type: Knowledge BaseStatus: ApprovedOwner: Cloudberrie StudioVersion: 4.2.0Updated: 2026-07-17
GitHub Foundation Lessons
| Lesson | Operational rule |
|---|
| Organization ownership and commit authorship are different. | Repositories belong to cloudberrie-studio; commits are attributed through the local Git email. |
| A business contact email is not automatically a GitHub login. | accounts@ is the organization contact; cb-engops remains the owner account. |
| Private repositories can show 404. | Verify the signed-in browser account and organization membership before assuming deletion. |
| Local and remote initial commits create unrelated histories. | Use a deliberate merge and resolve README/.gitignore conflicts; do not force-push during routine initialization. |
| History correction is safest before collaboration. | Correct attribution while a repository is new, then avoid rewrites once deployments and team workflows depend on commit hashes. |
| Infrastructure documentation must follow the actual implementation. | Capture real values, screenshots, errors, and validated resolutions. |