Shared guidance for proposing and reviewing changes in Geeksblock repositories.
GitHub uses the contribution guide and templates here when an organization repository has no local equivalent. Local files take precedence. Any valid local issue template or issue-template configuration suppresses the entire inherited issue-template folder; issue forms do not merge across repositories. These defaults do not replace a project's architecture, acceptance checks, release procedure or agent instructions.
This repository is public because GitHub requires public visibility for inherited community files. Keep its contents generic. Store customer information, credentials, deployment details and internal operational records in their authorized private locations.
Templates help people provide evidence; they do not enforce merge rules. Protect branches and configure real checks in each project's GitHub settings. A merge, a release, a deployment and user acceptance are separate milestones.