Deprecated - Other Solutions for users? about azure-repos-vscode HOT 18 CLOSED

I use it every time I checkin to "Associate work items". Is there some other extension or work flow that does that now that this extension is going away?

from azure-repos-vscode.

Would be nice if there was something like the GitHub Pull Requests and Issues extension for Azure DevOps.

https://github.com/microsoft/vscode-pull-request-github

from azure-repos-vscode.

Looking for "Create Pull Request" feature, too.

from azure-repos-vscode.

I used the extension primarily with Git on Azure DevOps.

Apart from 'Create Pull Request' feature, I also got used to a shortcut to the team project website.

Is there a chance that everything that's not related to TFVC be migrated to a new extension, i.e. Azure DevOps?

from azure-repos-vscode.

Agreed. Loved the "Create Pull request" feature. Also looking for alternatives.

from azure-repos-vscode.

Also like to thank you for this extension. I love it, and sad to see it go.

from azure-repos-vscode.

It's unfortunate to see this happen. A lot of us are already forced to use TFVC and this helped to at least make it a little less painful.

from azure-repos-vscode.

Why is this being deprecated? I understand TFVC decline but what about git functionality and git pull requests on Azure DevOps?
Thank you

from azure-repos-vscode.

@vtbassmatt , could you provide some clarifications?

I don't think anyone uses the extension with TFVC and the decline in popularity could probably be attributed to the critical bugs in the extension that weren't fixed for years (2 pages of issues on the "team:SignIn" alone, ex: #371 ). I'm not sure how one can expect something to be popular if you can't even start using the bloody thing. 😄

On the other hand, I can agree with the most folks - i don't really care about the SVC functionality, what i do care about is the project interaction features (create pull requests, build status (if i'd work correctly), work items etc).

Is it possible that you would reconsider complete deprecation, only remove TFVC support and re-purpose this extension as "Azure DevOps Team Project" or something?

It is really comfy (when it works).

from azure-repos-vscode.

Hey folks. Sorry, I didn't notice this thread until someone pinged me by name.

There isn't a lot more I can add, mostly because I don't have all the history on our (lack of) investment in the extension. When I picked up this project, it was already languishing. As you pointed out, bugs left unfixed for years lead to declining usage. I'm guessing that helped drive the decisions to pull back investment, a downward spiral that's hard to pull out of.

I'm going to spare you the sob story, the alternatives considered, and all that. There's simply no team available to pick this extension up again. I will point out that the extension is MIT licensed so other projects are free to use components if they'd like.

Gee I wonder if somebody could fork this repo, rip out the TFVC broken stuff, and publish a new extension to the marketplace while also fulfilling the terms of the MIT license.

from azure-repos-vscode.

Yeah! Of course I agree that the use of TFVC has declined but I am using it with Git.
please consider keeping useful features, or even better, merge all useful features of all extensions to a new Azure DevOps extension!

from azure-repos-vscode.

I agree on "Create Pull Request" and would also add "View Build Summary" to the list of desirable features to reimplement elsewhere (Azure Pipelines?)

from azure-repos-vscode.

Agree with what is said above. The create-pull-request is super handy. Also exclusively using it with Git.

So while I can imagine the business decision behind dropping TFVC, it's really hard to say goodbye to these QOL improvements for git.

from azure-repos-vscode.

I realy hope that one developers sees this :(

from azure-repos-vscode.

I use this at work and im a bit scared and confused. What does this mean? Does it mean we can't use source control with git in vscode anymore or is it only TFVC or are we just screwed in general? Do we manually have to upload files to our Azure DevOps repos?

from azure-repos-vscode.

To answer your questions:

• You will be able to use git from within VS Code
• You will not be able to use TFVC from within VS Code
• Unknown if you can use SSO with Azure DevOps with Git repos from within VS Code. I have to test this for my team :( I'm assuming the Azure Accounts extension with the Git Credential Manager will allow SSO. Can somebody from Microsoft address this question?

from azure-repos-vscode.

Hey folks. Sorry, I didn't notice this thread until someone pinged me by name.

There isn't a lot more I can add, mostly because I don't have all the history on our (lack of) investment in the extension. When I picked up this project, it was already languishing. As you pointed out, bugs left unfixed for years lead to declining usage. I'm guessing that helped drive the decisions to pull back investment, a downward spiral that's hard to pull out of.

I'm going to spare you the sob story, the alternatives considered, and all that. There's simply no team available to pick this extension up again. I will point out that the extension is MIT licensed so other projects are free to use components if they'd like.

from azure-repos-vscode.

Hadn't ever been to this Github repo until now. We've had entire teams who have installed and been hoping to continue using this extension. The extension has had a bug we've all seen here for a while now that we hoped was being resolved. (It complains that we need to use TFVC Local workspaces when we are all already, in fact, using Local, not Server, workspaces.) I'm immensely disappointed to see today that this is being retired. Yes, our use has gone down as we've be forced to use Visual Studio for managing TFVC check-ins, but it's only been because of the bug that's been present with this extension for so long. Really sad to see this waning support. We literally have hundreds of devs on our project and will continue to use TFVC into the future. Git-based repos (even larger ones) still just can't hold a candle to it for what we're doing. (features, performance, productivity, etc.) This extension had lots of promise.

from azure-repos-vscode.