Software design is weird. I wrote this article about implementing a minimal kanban board and the trade-offs I needed to make.
Software design is weird. I wrote this article about implementing a minimal kanban board and the trade-offs I needed to make.
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.