The community health repository for the Celo-HaiTi (CeloHT) GitHub organization.
This repository provides shared, organization-wide defaults so that every Celo-HaiTi repository — CeloHT, celoht-research, celoht-brand, and any future repository — inherits a consistent, professional community experience without duplicating the same files everywhere.
| File / Folder | Purpose |
|---|---|
profile/README.md |
The README shown on the public GitHub organization profile |
bug_report.md and bug_report.yml |
Default bug report issue template |
feature_request.md and feature_request.yml |
Default feature request issue template |
CODEOWNERS |
Default review routing |
CODE_OF_CONDUCT.md |
Org-wide community standard |
CONTRIBUTING.md |
Org-wide contribution guide |
SECURITY.md |
Org-wide security policy |
SUPPORT.md |
Where to get help |
FUNDING.yml |
GitHub Sponsors button configuration |
GOVERNANCE.md |
How CeloHT makes decisions |
MAINTAINERS.md |
Who maintains what, and how to become one |
COMMUNITY.md |
Community spaces and participation pathways |
LICENSE |
Apache 2.0 |
GitHub automatically falls back to the files in this repository — CODE_OF_CONDUCT.md, CONTRIBUTING.md, SECURITY.md, SUPPORT.md, issue templates, and more — for any repository in the CeloHT organization that doesn't define its own copy. This keeps every repository consistent by default, while still letting an individual repository override any file with its own version when it genuinely needs to.
profile/README.md is the one exception with a different mechanism: GitHub renders it directly as the organization's public profile page.
The main CeloHT documentation repository is the authoritative source for program, governance, and policy detail (GOVERNANCE.md, NO_TOKEN_POLICY.md, SECURITY.md, and so on). The files in this repository are intentionally shorter, org-wide-appropriate summaries that link back to that authoritative detail rather than duplicating it — see each file for its specific link-back. When something changes in the main documentation repository's governance or security policy, the corresponding summary here should be updated in the same pull request cycle, not left to drift.
See CONTRIBUTING.md. Changes here affect every Celo-HaiTi repository's default experience, so pull requests touching CODE_OF_CONDUCT.md, SECURITY.md, or GOVERNANCE.md require documented maintainer and governance review, consistent with the elevated-review pattern used across Celo-HaiTi repositories.