You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
If you program on a file and revert all the changes, GTM includes the time spent on coding on that file in the next commit. That is reasonable. However, when you create a new file after the last commit and spend time coding on it but don't include it in the next commit, GTM still includes the time spent on coding that file in the commit, even although you haven't committed these changes yet.
To Reproduce
Create a new file after the last commit and spend time coding on it
Commit other changes
=> GTM also includes the time you spent coding on that new uncommitted file in the next commit
Expected behavior
GTM should not include time spent on uncommitted changes in a commit. No matter if the file is new or not.
Screenshots/Logs
The files are not committed:
But GTM includes them in the report:
(and the time is not in status anymore since it has been committed)
Desktop:
OS: macOS
Version: 1.0.3
Additional context
Is there any way to revert this bug and exclude the time spent on these files out of that commit where they haven't been committed so the time spent on them will be counted for the actual commit where they will be committed?
The text was updated successfully, but these errors were encountered:
Hey,
I can completely understand that when being busy and just having much to do for school / uni / work / etc., you often don't have much time for private projects and such stuff.
I just wanted to ask if you have any plans to look into this and resolve it sometimes, since I can imagine you forgot about it.
It's still an issue I've encountered and since I like and use GPT, it would be nice to have it fixed sometimes.
But I completely understand if you currently have much on your mind, I just thought giving a reminder so maybe when you have more time you could look into it for a bit would be a good idea. :)
Describe the bug
If you program on a file and revert all the changes, GTM includes the time spent on coding on that file in the next commit. That is reasonable. However, when you create a new file after the last commit and spend time coding on it but don't include it in the next commit, GTM still includes the time spent on coding that file in the commit, even although you haven't committed these changes yet.
To Reproduce
=> GTM also includes the time you spent coding on that new uncommitted file in the next commit
Expected behavior
GTM should not include time spent on uncommitted changes in a commit. No matter if the file is new or not.
Screenshots/Logs
The files are not committed:
But GTM includes them in the report:
(and the time is not in status anymore since it has been committed)
Desktop:
Additional context
Is there any way to revert this bug and exclude the time spent on these files out of that commit where they haven't been committed so the time spent on them will be counted for the actual commit where they will be committed?
The text was updated successfully, but these errors were encountered: