Uncommitted files after implementing a track

[benjidotsh]

Hey guys 👋

First of all: thanks a lot for the great work with Conductor - it has made Gemini CLI my go-to tool for getting work done!

While Conductor is great at instructing to make automatic commits, I have noticed that whenever I complete implementation of a track, I still have a few uncommitted files that I have to commit manually. (or rather: let Gemini commit manually 😁)

After the implementation, it seems to mark the track as done and update the product documentation and that's what doesn't seem to get committed automatically.

Not sure if it's relevant, but whenever it asks what it should do with the track, I always pick option C. (Skip: Do nothing and leave it in the tracks file)

I have 0 experience contributing to anything related to AI, but I'm happy to take a stab at it myself if anyone can give some guidance. I have already looked into the code and I suppose the workflow.md file is the culprit, but I'm not 100% sure.

[sherzat3]

Great catch, @benjidotsh ! It seems we overlooked the final commit for documentation updates at the end of a track. Our team will take care of this, but in the future, feel free submit PRs right away for improvements you notice, and we’ll be happy to review them.

To answer your question, I think it's more likely the latter part of implement.toml.