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
Right now extensions can create SCM source control but there is no way to access current active source control instance. It would be great if we can access them like how to access active text editor, the API can be like
Kai Maetzel (@kieferrm)Peng Lyu (@rebornix) +1! Being able to retrieve the active SourceControl instance would be valuable for Live Share as well. I’d love to see this become possible 😁
Jonathan Carter (@lostintangent) Retrieving active source control provider is one solution for our multi-root workspace scenario but we didn't make decisions yet, you can join our discussion in microsoft/vscode#51734
Activity
[-]Short term roadmap[/-][+]Short term roadmap - DRAFT[/+]rebornix commentedon Jun 11, 2018
Right now extensions can create SCM source control but there is no way to access current active source control instance. It would be great if we can access them like how to access active text editor, the API can be like
lostintangent commentedon Jun 16, 2018
Kai Maetzel (@kieferrm) Peng Lyu (@rebornix) +1! Being able to retrieve the active SourceControl instance would be valuable for Live Share as well. I’d love to see this become possible 😁
egamma commentedon Jun 18, 2018
// João Moreno (@joaomoreno) fyi
rebornix commentedon Jun 18, 2018
Jonathan Carter (@lostintangent) Retrieving active source control provider is one solution for our multi-root workspace scenario but we didn't make decisions yet, you can join our discussion in microsoft/vscode#51734
[-]Short term roadmap - DRAFT[/-][+]Short term roadmap[/+]ha404 commentedon Jul 11, 2018
Awesome work guys! Can't wait to use this, been following it closely, gonna be a game changer in the productivity department for sure 😄
Merge pull request #1 from Microsoft/pr/yoh1496/590
Remove isTrusted from prComments markdown (#1)