chihlasm/resolutionflow
1
0
Fork 0
Code Issues 23 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

User Trees - database schema #12

New Issue
Closed
opened 2026-02-03 04:41:18 +00:00 by chihlasm · 1 comment
chihlasm commented 2026-02-03 04:41:18 +00:00 (Migrated from github.com)
Copy Link

Create user_trees table for personal/forked trees:

  • Create Alembic migration
  • Fields: user_id, forked_from_tree_id, name, tree_content (JSONB), visibility, share_token
  • Add session_custom_steps table to track custom steps per session
  • Add indexes for user lookup and share token

Reference: PHASE-2.5-PERSONAL-BRANCHING.md

Create user_trees table for personal/forked trees: - [ ] Create Alembic migration - [ ] Fields: user_id, forked_from_tree_id, name, tree_content (JSONB), visibility, share_token - [ ] Add session_custom_steps table to track custom steps per session - [ ] Add indexes for user lookup and share token Reference: PHASE-2.5-PERSONAL-BRANCHING.md
chihlasm commented 2026-02-03 05:13:44 +00:00 (Migrated from github.com)
Copy Link

Already implemented via user_folders table and author_id on trees. Users can organize trees in personal folders.

Already implemented via user_folders table and author_id on trees. Users can organize trees in personal folders.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
10x-analysis
From 10x product analysis
 backend
FastAPI/Python work
 bug
Something isn't working
 collaboration
Team sharing, escalation, notifications
 database
PostgreSQL/schema changes
 documentation
Documentation updates
 duplicate
This issue or pull request already exists
 enhancement
Improvement to existing feature
 feature
New functionality
 frontend
React work
 good first issue
Good for newcomers
 help wanted
Extra attention is needed
 integration
PSA, external service integrations
 intelligence
Analytics, AI, data-driven features
 invalid
This doesn't seem right
 priority: high
Do this soon
 priority: low
Nice to have
 priority: medium
Important but not urgent
 question
Further information is requested
 quick-win
Low effort, high value
 strategic
Long-term strategic bet
 ux
User experience improvements
 wontfix
This will not be worked on
No Label backend database feature priority: medium
Milestone
No items
No Milestone Phase 2.5
Projects
Clear projects
No project
Assignees
Clear assignees
chihlasm
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: chihlasm/resolutionflow#12
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?