Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Azure DevOps integration for git related promotion steps #3120

Closed
1 of 3 tasks
diegocaspi opened this issue Dec 11, 2024 · 0 comments · Fixed by #3128
Closed
1 of 3 tasks

Azure DevOps integration for git related promotion steps #3120

diegocaspi opened this issue Dec 11, 2024 · 0 comments · Fixed by #3128

Comments

@diegocaspi
Copy link
Contributor

diegocaspi commented Dec 11, 2024

Checklist

  • I've searched the issue queue to verify this is not a duplicate feature request.
  • I've pasted the output of kargo version, if applicable.
  • I've pasted logs, if applicable.

Proposed Feature

Add native Azure DevOps integration for the following steps in Kargo:

  1. git-open-pr: Support creating pull requests for repositories hosted on Azure DevOps.
  2. git-wait-for-pr: Support waiting for pull requests to be approved and merged within Azure DevOps.

Motivation

Currently, Kargo provides support for managing Git operations (such as creating and monitoring pull requests) via its git-open-pr and git-wait-for-pr steps. However, these steps seem to lack native support for Azure DevOps, which limits the tool’s usability for teams leveraging this platform for Git hosting and CI/CD workflows.

As Azure DevOps is a widely used tool for Git repository management, adding support for these steps would enhance Kargo’s versatility and make it more appealing to a broader user base.

Suggested Implementation

Add the azure git provider inside internal/gitprovider folder.

Notes

I'm already working on a PR for a first implementation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants