26
The Most Minimal Kanban
(fd93.me)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 30 Aug 2025
26 points (93.3% liked)
Programming
28322 readers
655 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 3 years ago
MODERATORS
FYI it's entirely possible to track multiple branches with unrelated histories in git. Both the task management and code can live in the same repository.
You could theoretically even give each task an ID, then tag commits in the code that complete those tasks with those task IDs.
This gives me some ideas for how it could be done that might be fun to explore. It comes with the benefit of not being platform-specific (GitHub/GitLab/etc). Merge conflicts might be annoying, but maybe there's a way to take advantage of Git's tree to represent relationships between tasks, and have one "HEAD" commit (or branch or other ref) per task? Not sure how this will work honestly.