[feat] Track changes to a user's project with a git repo #280

Activity

1. tcdent

   added a sub-issue on Feb 5, 2025

   • [feat] One command framework switch #265
2. tcdent

   self-assigned this

   on Feb 5, 2025
3. braelyn-ai commented on Feb 5, 2025

   

   braelyn-ai

   on Feb 5, 2025

   Last edited by braelyn-ai

   Contributor

   More actions

   idk if agentstack repo commit is necessary if they can just git commit. i think we should also have a flag for each command like --no-commit if you dont want to commit

   also i think we want to only git add the files we touched and make sure to not commit the user's other modified files. only commit unsaved changes if we're modifying a file that is already modified since the last commit

   open to discussion on this
4. tcdent commented on Feb 5, 2025

   

   tcdent

   on Feb 5, 2025

   Last edited by tcdent

   CollaboratorAuthor

   More actions

   idk if agentstack repo commit is necessary if they can just git commit. i think we should also have a flag for each command like --no-commit if you dont want to commit

   that makes sense!

   also i think we want to only git add the files we touched and make sure to not commit the user's other modified files. only commit unsaved changes if we're modifying a file that is already modified since the last commit

   thinking behind this was to separate our changes from theirs. if we change a file that they have changed (likely in a repo with 6 files) the commit gets muddied up. so we commit the current state of the project (if it's been changed) and then create a separate commit for the automated stuff.
5. tcdent commented on Feb 13, 2025

   

   tcdent

   on Feb 13, 2025

   CollaboratorAuthor

   More actions

   This has been released.
6. tcdent

   closed this as completedon Feb 13, 2025