Projectfile
Core Go library shared by every projectfile.org tool: pf-cli, pf-bridge and pf-ci. It parses, resolves and validates projectfiles against the embedded v1 schema, exposing the typed model the tools build on. Published as a Go module for reuse across the projectfile fleet.
Updated 2026-10-26 21:25:03 +00:00
pf-bridge is the projection tool of the projectfile: it derives forge identity files, assembles feature and roadmap fragments, and projects the projectfile onto the files a forge and repository expect. Companion binary to pf-cli for the projectfile.org tooling.
Updated 2026-10-26 20:58:02 +00:00
pf-cli is the command-line frontend for the projectfile: it reads, writes and validates fields, resolves remote includes, and generates derived artifacts. It embeds the v1 JSON Schema for offline validation and is the canonical tool for editing projectfiles locally and in CI.
Updated 2026-10-26 20:57:49 +00:00
pf-ci lowers the vendor-neutral org.projectfile.ci signal DAG to concrete CI workflow files for Forgejo Actions and GitHub Actions, dispatching each provider leaf to its recipe in projectfile/actions. Companion binary to pf-cli for the projectfile.org tooling.
Updated 2026-10-26 20:57:46 +00:00
The normative specification of the projectfile: a single stack- and vendor-agnostic YAML file that describes a software project identity, build, CI and publishing. Holds the spec prose and v1 JSON Schema, dual-licensed MIT and CC-BY-4.0, rendered at projectfile.org and consumed by the pf-cli, pf-bridge and pf-ci tools.
Updated 2026-10-26 20:57:33 +00:00
The external provider action library for pf-ci. Each provider name maps to one composite action, pinned and consumed as /actions/@v1 — the owner being this library’s mirror on whichever forge the workflow runs on; the resolver keeps the dispatch while this library owns the native CI recipe for each target (Ports and Adapters).
Updated 2026-10-25 19:10:38 +00:00