Contribute¶
- Contributing workflow
- Dependency management
- Documentation authoring
- Python documentation
- Python static analysis
- Router architecture
- API authoring standard
- Windows image-build WSL environment
- Atlaso UI Design Guide
- Detailed agent policies
- Security policy
- Code of conduct
Every repository change starts with a labeled issue and ends with a reviewed pull request that closes it. Run the
focused local tests, documentation validation, applicable repository checks, and git diff --check before delivery.
GitHub CI owns the complete Python test suite. Automated contributors keep the originating task active to follow
current-head checks, comments, reviews, and review threads through completion. After an authorized merge and all
post-merge activity, the primary-checkout controller deletes the task-owned GitHub branch with an atomic expected-SHA
lease, removes the Codex worktree, deletes the exact local task branch, and only then appends " · Done" to the task title.
Interrupted cleanup can resume
after worktree removal only with the same task, head, and merge evidence. Primary-checkout tasks instead restore a
clean checkout to current
origin/main and delete the exact local task branch, with fail-closed resume from an interrupted clean main state.
A runtime without supported title controls records the title state
as not applicable with capability evidence; failed available cleanup operations leave the task actionable.
Validated sensitive vulnerabilities use the private advisory and temporary-fork workflow in the
Security policy instead of a public issue or public pull
request. The ordinary version, local validation, and review requirements remain in force; required local validation
replaces unavailable GitHub CI for temporary private forks. Their sanitized tasks become cleanup-ready only after an
authorized advisory merge is on main and coordinated release, disclosure, and remaining advisory activity finish.