GitHub Repository Guidance
This page records the naming convention we have agreed for Developer Experience repositories and how we intend to create and use repositories going forward.
Naming convention
Repositories owned by the Developer Experience team should use lowercase kebab-case and follow this pattern:
developer-experience-<product-or-capability>[-<type>]
The optional suffix can be used when it makes the purpose clearer, for example api, ui, docs, config, infra, or template.
Repository management
Create repositories per product, service, or distinct capability, and only combine work into a shared repository when it is tightly coupled and delivered as one product.
New repositories should be created via octo-access.
The current repository list is maintained on the OCTO Developer Experience repositories team page.
This gives us a stable team namespace, makes ownership clearer, and keeps the repo set easy to discover.