Org-level configurations, reusable workflows, community health files, and agentic workflow templates for the Drasi project.
.github/workflows/ Reusable CI workflows (called via workflow_call)
├── rust-unit-test.yaml Rust test: caching, Redis, system deps, toolchain
├── rust-lint.yaml Rust lint: clippy + fmt, caching, system deps
├── cargo-audit.yaml Dependency vulnerability scanning (cargo audit + cargo deny)
└── devskim.yaml Microsoft DevSkim security scanner with SARIF upload
workflow-templates/ Starter templates (shown in Actions → New workflow)
├── rust-unit-test.yml Rust tests
├── rust-lint.yml Rust lint
├── cargo-audit.yml Cargo audit
├── devskim.yml DevSkim security scan
├── pr-assignment-check.yml PR assignment check
├── pr-first-approval-label.yml PR review trigger (Stage 1)
└── pr-first-approval-label-run.yml Label on first approval (Stage 2)
(each .yml has a matching .properties.json)
agentic-workflows/ Copilot agentic workflow source files (.md)
├── README.md Setup and sync instructions
└── drasi-issue-researcher.md
ISSUE_TEMPLATE/ Org-default issue forms
├── bug.yaml
├── feature.yaml
├── engineering.yaml
└── config.yaml
CODE_OF_CONDUCT.md Inherited by all repos without their own
CONTRIBUTING.md Inherited by all repos without their own
SECURITY.md Inherited by all repos without their own
pull_request_template.md Inherited by all repos without their own
AI_POLICY.md AI usage policy
MENTORSHIP.md Mentorship program info
CHECKLIST.md Per-repo migration checklist
LICENSE Apache-2.0
profile/README.md Org profile (github.com/drasi-project)
Repos call centralized CI workflows instead of duplicating pipeline definitions:
# In any Drasi repo
jobs:
test:
uses: drasi-project/.github/.github/workflows/rust-unit-test.yaml@main
lint:
uses: drasi-project/.github/.github/workflows/rust-lint.yaml@main
audit:
uses: drasi-project/.github/.github/workflows/cargo-audit.yaml@main
devskim:
uses: drasi-project/.github/.github/workflows/devskim.yaml@mainSee each workflow file for available inputs and defaults.
GitHub automatically inherits these files for any repo in the drasi-project org that doesn't define its own:
CODE_OF_CONDUCT.mdCONTRIBUTING.mdSECURITY.mdISSUE_TEMPLATE/pull_request_template.md
A repo can override any of these by adding its own version.
When someone clicks Actions → New workflow in any org repo, they'll see Drasi-specific templates (e.g., "Drasi Rust Unit Tests", "Drasi Rust Lint") auto-suggested when a Cargo.toml is detected.
Copilot agentic workflows cannot be called cross-repo. The .md source files are maintained here as the single source of truth, but must be copied to each repo and compiled with gh aw compile. See agentic-workflows/README.md for instructions.
See CHECKLIST.md for the full per-repo migration/onboarding checklist.