No description
- Shell 52.1%
- Makefile 29.8%
- Python 18.1%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
Damián Búho
908b573eef
ci-check and ci-generate are hand-written recipes in core/ci/030-generate.mk, not portable commands. Undeclared, they were dangling needs — and a dangling need is a TOOL by spec, so the forge lowering rendered them as a bare `run: ci-check` and every runner failed with exit 127, command not found. Declare both as manifest tools with NEITHER `run` NOR `image`, so each stays a pure DAG-membership placeholder whose native recipe survives (the same shape `fetch` already uses), plus gha/forgejo: false to prune them from both cloud lowerings. pf-ci is host-only by design: a runner cannot regenerate the very workflow it is executing. The m6e lowering already guarded this exact case at recipe emission; only the forge side lacked the equivalent, so the two lowerings now agree. |
||
| base | ||
| ci | ||
| docs | ||
| goals | ||
| LICENSES | ||
| meta | ||
| scripts | ||
| tests | ||
| tools | ||
| traits | ||
| workflow | ||
| .gitignore | ||
| ci.yaml | ||
| CITATION.cff | ||
| CODE_OF_CONDUCT.md | ||
| CODEOWNERS | ||
| cog.toml | ||
| CONTRIBUTING.md | ||
| conventions.yaml | ||
| initialize.mk | ||
| lefthook.yaml | ||
| LICENSE | ||
| projectfile.yaml | ||
| README.md | ||
| ruff.toml | ||
| SECURITY.md | ||
M6E Core Library
Core Makefile framework providing variables, git state, CI workflows, scenario DAG, and universal linters.
Documentation
- The
org.projectfile.cisignal DAG (and the build matrix) - Caching = mounts
- Events
- FAQ — the questions you hit on day one
- User Hooks
- m6e-run
- Writing a target
Policies
Links
Project
License
This project is licensed under MIT — see the LICENSE file for details.