To build and release Dagger, we compute and inject a version string. We do this in a way that is slow, breaks separation of concerns, and increases complexity and bugs.
Specifically, the current implementation:
---
name: bullet-style
description: Write tight, parallel-structured bullets for technical problem statements, RFC critique sections, GitHub discussion intros, and design doc analysis. Use when drafting or editing prose where bullets describe how a system behaves and why it's problematic. Triggers on: problem statement, RFC, design doc critique, discussion intro, bulleted analysis, "what's wrong with X."
---
A distilled style guide for technical bulleted critique — problem statements, RFC sections, GitHub discussion intros, anything where a bulleted list describes how a system works and why it's bad.
Markers in the rules below: ✅ explicitly taught through edits;
Build a standalone CLI that mirrors Discord thread state into SQLite.
The tool must not depend on discordex internals. It should be usable by discordex, an admin script, or any other consumer as an external process that owns its own config, Discord connection, database, migrations, and inspection commands.
Yves (eunomie) has an open PR — dagger/dagger#13130 — adding dagger module-checks, a new experimental command that fetches check/trace results from Dagger Cloud and renders them in the CLI. It works, but it's a separate command with its own rendering pipeline, disconnected from the existing dagger check.
Don't add a new command. Make dagger check smarter.
Running tracking doc for the original workspace-artifacts design session. Superseded by the Modules v2 design docs.
See: https://github.com/dagger/dagger/tree/modules-v2/hack/designs/modules-v2
Analysis concluding that typed collection filters collapse the need for a
separate artifact address concept. The conclusion is incorporated into
hack/designs/modules-v2/artifacts.md on the modules-v2 branch of
dagger/dagger.
See: https://github.com/dagger/dagger/tree/modules-v2/hack/designs/modules-v2
Working notes from the design session that produced the Modules v2 split docs.
Covers the Artifacts API schema evolution, Execution Plans, filter model,
Action type, and staged changes to collections. Content has been absorbed into
hack/designs/modules-v2/ on the modules-v2 branch of dagger/dagger.
See: https://github.com/dagger/dagger/tree/modules-v2/hack/designs/modules-v2
This document is archived. It was the original integrated design covering
collections, addresses, verbs, plans, and provenance as one system. It has
since been superseded by the split design docs in hack/designs/modules-v2/
on the modules-v2 branch of dagger/dagger.
See: https://github.com/dagger/dagger/tree/modules-v2/hack/designs/modules-v2