Feature summary
Allow the addition of ADO Accounts
What problem are you trying to solve?
At work we are limited to using ADO for the foreseeable future as all of our legacy code, PRs, and issues are there. I would love to use this flow (multiple project repos, feature planning, issue creation, automation) to work through my current set of issues and PRs in ADO using AI.
Proposed solution
I'd propose that you expand Accounts to include ADO accounts as well. This would involve account creation, management, and azure devops specific connections (Azure CLI, API, etc.) among other things no doubt.
Workflow impact
I believe this affects a large group of underrepresented developers that are still using ADO within various large, legacy enterprises but are active GitHub Copilot users via VS Code, etc.
Installation context
n/a
Additional context
Thank you so much for your work on this so far! I'm really excited to put this app through its proper paces, but I find the lack of ADO support holding me back from diving in. While most AI forward solutions seem to be heavily GitHub focused, I'd love to see the ADO folks brought along for the ride (especially from Microsoft adjacent solutions). Frameworks like squad from Brady Gaster have pushed in this direction recently (https://bradygaster.github.io/squad/blog/025-squad-goes-enterprise-azure-devops/) and, while not perfect, have really helped me to experiment with and adopt some AI workflows while still using ADO.
Feature summary
Allow the addition of ADO Accounts
What problem are you trying to solve?
At work we are limited to using ADO for the foreseeable future as all of our legacy code, PRs, and issues are there. I would love to use this flow (multiple project repos, feature planning, issue creation, automation) to work through my current set of issues and PRs in ADO using AI.
Proposed solution
I'd propose that you expand Accounts to include ADO accounts as well. This would involve account creation, management, and azure devops specific connections (Azure CLI, API, etc.) among other things no doubt.
Workflow impact
I believe this affects a large group of underrepresented developers that are still using ADO within various large, legacy enterprises but are active GitHub Copilot users via VS Code, etc.
Installation context
n/a
Additional context
Thank you so much for your work on this so far! I'm really excited to put this app through its proper paces, but I find the lack of ADO support holding me back from diving in. While most AI forward solutions seem to be heavily GitHub focused, I'd love to see the ADO folks brought along for the ride (especially from Microsoft adjacent solutions). Frameworks like squad from Brady Gaster have pushed in this direction recently (https://bradygaster.github.io/squad/blog/025-squad-goes-enterprise-azure-devops/) and, while not perfect, have really helped me to experiment with and adopt some AI workflows while still using ADO.