Closed jwooley closed 9 years ago
Thanks! Do you have a PR ready?
Not yet. I just pulled a clone, but not sure if I'll have much time over the next week to create a PR.
I will boot an Azure VM, and see what I can do, @jwooley
I can fix the code but I don't use Git.
@dothenrik if you can fix, email me changes, and I will update repo and new nuget package
Attempt to fiox for CTP6 and uploaded new NuGet package (tests still need fixing)
Looks like there are issues with the hint path (to your local folder) for the SQL ScriptDOM library. Also, the interpolated string test is failing due to changes in C#6 interpolation implementation. I have a fix, but get a 403 trying to push. I didn't fork before trying the changes.
Hi Jim,
It's not too late to fork the repository now. In fact, it's normal and common for a single working folder on your computer to point to two or more different locations where the code is stored remotely, and you can even change/add/remove those locations whenever you want. For your purposes, I believe the following steps are the easiest since you already cloned this GitHub repository.
On your computer from a command prompt, run the following command:
git remote -v
If the previous command listed the origin
remote as starting with git@github.com:DotNetAnalyzers
, run the following command:
git remote set-url origin git@github.com:jwooley/TSqlAnalyzer.git
Otherwise, if the previous command listed the origin
remote as starting with https://github.com/DotNetAnalyzers
, run the following command:
git remote set-url origin https://github.com/jwooley/TSqlAnalyzer.git
After the above steps, when you push your code, it will push to your fork instead of trying to push to this repository (which you do have permissions for). :+1:
Analyzer is not recognized with VS 2015 CTP6.