-
Notifications
You must be signed in to change notification settings - Fork 8
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
Visix for SSMS #9
Comments
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. |
Interesting idea
…On 27 December 2017 at 07:58, Jay Asbury ***@***.***> 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>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The text was updated successfully, but these errors were encountered: