Member Access
Invite contributors by exact GitHub username. Start with member access, then promote only trusted maintainers who need organization settings.
Organization handbook
Use this page to keep member access, repository standards, launch readiness, and security expectations easy to follow.
Repos stay open, docs stay readable, and maintainers keep decisions visible.
Invite contributors by exact GitHub username. Start with member access, then promote only trusted maintainers who need organization settings.
Each repo should include setup steps, API route docs, environment variable names, deployment notes, a license, and a security contact path.
Before publishing, confirm the landing README, examples, health route, error format, and deployment workflow are accurate.
Keep pull requests focused. Ask for review when behavior changes, tests are added, or public API responses are updated.
Never commit secrets. Use repository secrets for deploy tokens, rotate leaked keys immediately, and document required credentials by name only.
Enable SAML only after identity-provider details are tested. Keep SAML enforcement off until every active member has authenticated.