A loose federation of distributed, typed datasets
docs: add git workflow guidance for planning documents
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
+6
.chainlink/issues.db
.chainlink/issues.db
This is a binary file and will not be displayed.
+6
CLAUDE.md
+6
CLAUDE.md
···
158
158
- **Always include `.chainlink/issues.db`** in commits alongside code changes
159
159
- This ensures issue tracking history is preserved across sessions
160
160
- The issues.db file tracks all chainlink issues, comments, and status changes
161
+
162
+
### Planning Documents
163
+
164
+
- **Track `.planning/` directory in git** - Do not ignore planning documents
165
+
- Planning documents in `.planning/` should be committed to preserve design history
166
+
- This includes architecture notes, implementation plans, and design decisions