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 Additon #460

Open
LDavidBryant opened this issue May 3, 2024 · 6 comments
Open

Azure DevOps Additon #460

LDavidBryant opened this issue May 3, 2024 · 6 comments
Assignees
Labels
💎 Bounty Discussion Needs consensus enhancement New feature or request Needs Investigation This issue needs a team member to investigate its status.

Comments

@LDavidBryant
Copy link

Is your feature request related to a problem? Please describe.
We need to investigate the addition of support for Azure DevOps Git repositories.

Describe the solution you'd like
Access for teams/users to be able to utilize Azure DevOps repo's in their workflow, especially for larger teams over different locations.

@ivan-burazin as requested.

@LDavidBryant LDavidBryant added the enhancement New feature or request label May 3, 2024
@Tpuljak Tpuljak added Discussion Needs consensus Needs Investigation This issue needs a team member to investigate its status. labels May 10, 2024
@Tpuljak
Copy link
Member

Tpuljak commented May 22, 2024

/bounty $200

Copy link

algora-pbc bot commented May 22, 2024

💎 $200 bounty • Daytona

Steps to solve:

  1. Start working: Comment /attempt #460 with your implementation plan
  2. Submit work: Create a pull request including /claim #460 in the PR body to claim the bounty
  3. Receive payment: 100% of the bounty is received 2-5 days post-reward. Make sure you are eligible for payouts

If no one is assigned to the issue, feel free to tackle it, without confirmation from us, after registering your attempt. In the event that multiple PRs are made from different people, we will generally accept those with the cleanest code.

Thank you for contributing to daytonaio/daytona!

Add a bountyShare on socials

Attempt Started (GMT+0) Solution
🟢 @tarunrajput May 23, 2024, 3:58:28 PM #610

@Tpuljak
Copy link
Member

Tpuljak commented May 22, 2024

Because this issue is of a much broader scope than the usual bounties in our repository. We might assign collaborators that we feel should tackle solving it.

That being said, to get assigned, we would require that the collaborator shows us they understand the scope of the issue and a plan on how to implement certain Git Provider methods using the Azure DevOps API.

It is not a requirement to get assigned to the issue to start working on it, but if we end up assigning someone, we expect collaborators to respect that.

@tarunrajput
Copy link
Contributor

tarunrajput commented May 23, 2024

/attempt #460

Hey @Tpuljak, I'm planning to use the Azure DevOps Go SDK for this. I've already implemented two methods and will complete the remaining methods soon.

Algora profile Completed bounties Tech Active attempts Options
@tarunrajput    10 daytonaio bounties
+ 4 bounties from 4 projects
Java, TypeScript,
JavaScript
Cancel attempt

@abhishek818
Copy link

@Tpuljak adding myself in queue..

Copy link

algora-pbc bot commented May 30, 2024

💡 @tarunrajput submitted a pull request that claims the bounty. You can visit your bounty board to reward.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💎 Bounty Discussion Needs consensus enhancement New feature or request Needs Investigation This issue needs a team member to investigate its status.
Projects
None yet
Development

No branches or pull requests

4 participants