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
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
Majority of options are disabled in the contextmenu.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.
Create a merge conflict in your repository. In the merge conflict dialog, right click a file and try to "Save Local as". The option (amongst others) are disabled.
What is the expected behavior?
That the options are not disabled.
Which versions of GitExtensions, GIT and Windows are affected by this issue? Did this work in previous versions of our tool?
Windows 10, Git Extensions 2.5.0. Yes, worked in previous versions.
In previous versions I could "Save Local as" and keep a copy of the file locally while resolving the conflicts. I saw nothing in the release notes regarding this, so I'm posting this as a bug. Please correct me if I'm wrong!
The text was updated successfully, but these errors were encountered:
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
Majority of options are disabled in the contextmenu.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.
Create a merge conflict in your repository. In the merge conflict dialog, right click a file and try to "Save Local as". The option (amongst others) are disabled.
What is the expected behavior?
That the options are not disabled.
Which versions of GitExtensions, GIT and Windows are affected by this issue? Did this work in previous versions of our tool?
Windows 10, Git Extensions 2.5.0. Yes, worked in previous versions.
http://i.imgur.com/068xtu1.png
In previous versions I could "Save Local as" and keep a copy of the file locally while resolving the conflicts. I saw nothing in the release notes regarding this, so I'm posting this as a bug. Please correct me if I'm wrong!
The text was updated successfully, but these errors were encountered: