Hacker News
points by gosugdr 4 days ago | 0 comments
Nope, you're breaking Git history with that.

You should think about what your history represents. Just move the task manager somewhere else and track it there.

[–] svartskogen 4 days ago
I was doing something like this manually, but for my own solo-dev projects. I wonder if your opinion is still the same for this case. I totally understand this is not really working when working on a team, but for planning -> delegating to LLMs this works really well for me
[–] gosugdr 3 days ago
Better to keep tasks in a separate repo imo, or at least make sure they aren't committed.

I always follow one rule: looking at the git history should tell me what each change did, and the commit message alone should be enough to understand what actually changed.

If you mix tasks with code changes, you will just confuse your future self.

Moreover, you can set up something like beads to handle task delegation and status updates for your agents.

https://github.com/gastownhall/beads