Skip to content

Move idea/planned features out of chocks, into issues - #51

Draft
mattobee wants to merge 3 commits into
mainfrom
docs/move-ideas-to-issues
Draft

Move idea/planned features out of chocks, into issues#51
mattobee wants to merge 3 commits into
mainfrom
docs/move-ideas-to-issues

Conversation

@mattobee

@mattobee mattobee commented Aug 2, 2026

Copy link
Copy Markdown
Owner

Ideas and planned work belong in an issue tracker, not in the tree chocks manages itself. This moves every feature in this repo's own .chocks at idea or planned status to a GitHub issue: #41 (keyboard shortcuts, with #42 to #44 as its sub-issues), #45, #46, #47, #48, #49, #50.

released, pre-release, deprecated and dropped stay in chocks. Those are statements about what shipped, which is what chocks can actually see from the repo it lives in.

Also fixes a stale one along the way: Drag to reorder and reparent was marked idea, but the file describes exactly what dragging already does, and it's been e2e-tested for a while.

Last commit isn't mine. It's a rename and a delete made through the running app while this migration was in progress in the same tree, and I've kept it separate rather than folding it into the migration commit.

It was still status: idea, but the body describes exactly what dragging
does today, and it's been shipped and e2e-tested for a while.
Ideas and planned work belong in an issue tracker, not in the tree
chocks manages. Moves every idea and planned feature in this repo's own
.chocks to a GitHub issue: #41 (keyboard shortcuts, with #42-44 as its
three sub-issues), #45 (release checkpoint), #46 (releases in history),
#47 (removed features), #48 (links to issues and PRs), #49 (merge
conflict handling), #50 (static export).

released, pre-release, deprecated and dropped stay in chocks. Those are
statements about what shipped, which is what chocks can see from the
repo it lives in.
Made through the running app while the migration above was in progress
in this same tree.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant