What to prepare
- A DevOps server: infrastructure, CI/CD, monitoring, security, cloud or containers. You opt in by setting directory_categories for this list to one of its table sections.
- Recent commits on the source repository (no activity for 12 months is rejected).
A table row in a DevOps section
The service adds one row at the end of the table in the section you chose, linking your repository and describing it in one sentence, with the remote endpoint when the server is hosted.
Submission workflow
- Set directory_categories for this list to the section that fits; without it the list is shown as not applicable.
- Run the free preflight: it checks repository activity and scans the list and open pull requests.
- Review the exact table row.
- Authorize the checked contribution and follow the independently verified pull request.
- Listing is confirmed only when the row is on the default branch.
Blockers to resolve before review
Use these as preparation checks. The destination makes its own acceptance decision.
- No DevOps relevance, an experiment with no documentation, or an abandoned project.
- Duplicate functionality without differentiation, or broken links.
Primary sources
Checked 2026-11-04. Follow the destination’s current instructions if its requirements change.