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
GitButler can lose filemodes from files (mainly executable +x, from .sh files) when doing changes.
Also losing the filemode (as shown by git ls-files --stage) and manually adding it with git-update-index --chmod=+x file.sh in workspace is not displayed in any useful way and is not included in commit and push.
How to reproduce (Optional)
No response
Expected behavior (Optional)
No response
Relevant log output (Optional)
The text was updated successfully, but these errors were encountered:
Thanks a lot for reporting, and sorry for the hassle!
I believe this will be a thing of the past with the upcoming major release. GitButler still hides the index completely, but will handle it (and changes to it) correctly nonetheless.
To try out if commits would work already in said upcoming release, you can type v3 outside of anything editable and commit with it.
Version
0.14.13
Operating System
Windows
Distribution Method
msi (Windows)
Describe the issue
GitButler can lose filemodes from files (mainly executable +x, from .sh files) when doing changes.
Also losing the filemode (as shown by git ls-files --stage) and manually adding it with git-update-index --chmod=+x file.sh in workspace is not displayed in any useful way and is not included in commit and push.
How to reproduce (Optional)
No response
Expected behavior (Optional)
No response
Relevant log output (Optional)
The text was updated successfully, but these errors were encountered: