π Bug Description
sync_pending_state() marks files as status "committed" when they are no longer dirty in VS Code. These files have NOT been committed to GitHub β they were merely cleaned up locally or reverted.
π Steps to Reproduce
- Make changes to a file so it appears as staged.
- Discard the changes locally (revert to original).
- Check the file status in the database via the Telegram bot
/log command.
β
Expected Behavior
Files that were reverted or cleaned up locally should be marked as "cancelled" or "removed", not "committed".
β Actual Behavior
The status bar and Telegram bot show these files as "committed", polluting the commit history with phantom commits.
π Environment
| Field |
Value |
| OS |
Any |
| VS Code version |
Any |
| GitPhone extension version |
Any |
| Python version |
Any |
π Additional Context
File: backend/supabase_service.py:242-277
Fix: Change the status to "cancelled" or "removed" instead of "committed" when files are no longer dirty.
π Bug Description
sync_pending_state()marks files as status"committed"when they are no longer dirty in VS Code. These files have NOT been committed to GitHub β they were merely cleaned up locally or reverted.π Steps to Reproduce
/logcommand.β Expected Behavior
Files that were reverted or cleaned up locally should be marked as
"cancelled"or"removed", not"committed".β Actual Behavior
The status bar and Telegram bot show these files as "committed", polluting the commit history with phantom commits.
π Environment
π Additional Context
File:
backend/supabase_service.py:242-277Fix: Change the status to
"cancelled"or"removed"instead of"committed"when files are no longer dirty.