Tree forking API endpoint #13

New Issue

2026-02-03T04:41:21Z

chihlasm commented

2026-02-03 04:41:21 +00:00

(Migrated from github.com)

Create API for forking trees:

POST /api/v1/user-trees/fork/{tree_id} - Fork an official tree
Deep copy tree structure to user_trees
Track lineage (forked_from_tree_id, forked_at_version)
Increment fork_count on original tree

Reference: PHASE-2.5-PERSONAL-BRANCHING.md

Create API for forking trees: - [ ] POST /api/v1/user-trees/fork/{tree_id} - Fork an official tree - [ ] Deep copy tree structure to user_trees - [ ] Track lineage (forked_from_tree_id, forked_at_version) - [ ] Increment fork_count on original tree Reference: PHASE-2.5-PERSONAL-BRANCHING.md

chihlasm commented

2026-02-08 00:40:57 +00:00

(Migrated from github.com)

Core forking API implemented in PR #39. Three endpoints available: fork a tree, list forks, and get lineage chain. Implementation uses /\ lineage tracking on the trees table (not a separate \ table as originally spec'd). Deep copies tree structure and tracks fork depth/reason. 9 tests passing.

Core forking API implemented in PR #39. Three endpoints available: fork a tree, list forks, and get lineage chain. Implementation uses \/\ lineage tracking on the trees table (not a separate \ table as originally spec'd). Deep copies tree structure and tracks fork depth/reason. 9 tests passing.

chihlasm commented

2026-02-08 00:41:18 +00:00

(Migrated from github.com)

Correction: Implementation uses parent_tree_id/root_tree_id lineage tracking on the trees table (not a separate user_trees table as originally spec'd).

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: chihlasm/resolutionflow#13