-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change between branches generate commits #140
Comments
If I understand correctly, you mean that it show some changed files, not that it creates a commit? |
In this video you can see the issue. In this case, they are very little time in the screen, but I other cases remain as a common commit. https://www.dropbox.com/s/peple0knfqyypxm/FakeCommits.mov?dl=1 |
So yes, that's not a commit, that's just showing the current changed files until Kactus re-generate the sketch file. This is a bit weird and I haven't seen this behaviour before. I can't reproduce in my repos. Would it be possible for you to give me access to the repo? |
Sorry, I can't because it is confidential 😴 |
+1 |
Description
When I change between branches, Kactus generate a commit with a lot of file changes. This commit disappears if you let Kactus loading more time, but will be fantastic If this commit doesn't appear.
I understand that this is happening because there is a gap when Github change files between branches and when you are in the "new" branch you still have files from another branch.
Version
Steps to Reproduce
Expected Behavior
Change to another branch without seeing this commits
Actual Behavior
A lot of new commits appears
The text was updated successfully, but these errors were encountered: