Open vbjay opened 6 years ago
vbjay
commented
6 years ago Thoughts:
If in project, use that path to know which git repo to use. If not, use current path of current script to match the repo path to use. If the current script is not in a repo folder, disable all but repo creation and browse commands. If current script has no path, then again disable commands.
RussKie
commented
6 years ago Interesting idea
On 27 December 2017 at 07:58, Jay Asbury notifications@github.com wrote:
Thoughts:
If in project, use that path to know which git repo to use. If not, use current path of current script to match the repo path to use. If the current script is not in a repo folder, disable all but repo creation and browse commands. If current script has no path, then again disable commands.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/gitextensions/gitextensions/issues/4278#issuecomment-354012516, or mute the thread https://github.com/notifications/unsubscribe-auth/AEMyXpCuoNzk4JjDpouhsPhei1-BeZ5_ks5tEV3ggaJpZM4RNAHH .
vbjay
commented
6 years ago
Do you want to request a feature or report a bug? Feature What is the current behavior? Visix only installs to visual studio.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.
What is the expected behavior? SSMS uses the isolated shell, which is a VS shell, to show sql server management tools. I don't see why we can't make visix for SSMS also that would allow us to commit sql scripts. Environment you encounter the issue: NA
Did this work in previous version of GitExtensions (which)? No.