Azure Devops Pull Request Extension for VS Code | F5 - Squashing Bugs

[utterances-bot]

Azure Devops Pull Request Extension for VS Code | F5 - Squashing Bugs

Introducing Azure Devops Pull Request Extension for VS Code

https://ankitbko.github.io/blog/2021/01/azdo-pr-vscode-extension/

[sheldonhull]

@ankitbko fantastic start here. What do you think as a community member I could do to raise awareness wider on this great hackathon project and see about possibly advocating for more support and awareness on this.

I feel like this is a major missing piece to the Azure Repos experience as context requires almost all the PR collaboration to be in browser outside of the code base.

Some tools exist like Codestream which are promising, but require further tooling and approvals compared to leveraging the natively provided workflow.

Anyway, thank you for this extension. I had been thinking of this exact solution (github pr extension for azure devops) which I came across this project. 🎉

[ankitbko]

@sheldonhull glad you liked it. Please spread awareness about the extension, write blog post or share this with your colleagues and friends.
I am trying to add more feature to this to keep it in parity with Github PR extension so there is still a lot of work to be done. Any contributions in terms of issues, bugs, feature requests, PRs are very much welcomed.

[emb03]

Is there a easy way to see conflicts? Do you need to checkout the PR to see the conflicts? Great extension, thanks for your work, hope it continues.

[BorGru]

The URL of my GIT repository is https://dev.azure.com/<org_name>/Shareflex%20Solutions/_git/ShareflexQualityAudit. Which part is the organizatinal URL and which one is the project name. I tried to configure several combinations, but none worked.

[ankitbko]

@BorGru orgUrl will be https://dev.azure.com/<org_name> and project name will be Shareflex Solutions

[BorGru]

Thanx for the quick reply … I’ll give it a try tomorrow Von: Ankit Sinha ***@***.***> Gesendet: Dienstag, 16. November 2021 18:27 An: ankitbko/blog ***@***.***> Cc: Boris Grüning ***@***.***>; Mention ***@***.***> Betreff: Re: [ankitbko/blog] Azure Devops Pull Request Extension for VS Code | F5 - Squashing Bugs (#21) @BorGru<https://github.com/BorGru> orgUrl will be https://dev.azure.com/<org_name> and project name will be Shareflex Solutions — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#21 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AKVZXJQEUMS6NUFEFBMWML3UMKH4NANCNFSM46RHP6OA>. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[h-iggs]

This looks great. I'm looking forward to trying it out. But I do have a problem :)

[Info] AzdoRepository> projectName is THISISCORRECT
[Info] AzdoRepository> orgUrl is THISISALSOCORRECT
[Info] Looking for git repository
[Info] Git repository found, initializing review manager and pr tree view.
[Info] Review> Validate state in progress
[Info] Review> Validating state...
[Info] FolderRepositoryManager> No remote with name 'upstream' found. All other remotes: origin
[Info] FolderRepositoryManager> Found Azdo remotes origin
[Info] Review> no matching pull request metadata found for current branch feature/development
[Info] AzdoRepository> Fetching pull requests for search: {"sourceRefName":"feature/development"} failed: Error: A project name is required in order to reference a Git repository by name.

So the URL and project is correct. My project name does have a space in it. Any ideas? Thanks :)

[leonardo9311]

@h-iggs i have the same issue did you got anything?

[miguelsguedeshpp]

Hi, I can see a lot of potential in this extension for the organization I work in - but the main thing that is missing of us is a way of defining an external diff tool to see the differences in non text based files.
Is that something that can be done, and I've just missed it?
Thanks!