Suggestion to Add Support for Gitee in Git Provider or More Customization Options

[TS35]

Hello, could you add support for Gitee in the git-providers configuration for Daytona? Alternatively, it would be great if future versions of Daytona could include more customizable options for git-provider, similar to how the Server in Daytona allows for some customization through modifications to the config.json file.

[Tpuljak]

Hi @TS35,

We're definitely committed to adding support for any available git providers.

If you're up for it, you can implement it through a PR yourself. You can check implementations for existing providers here.

Alternatively, it would be great if future versions of Daytona could include more customizable options for git-provider, similar to how the Server in Daytona allows for some customization through modifications to the config.json file.

What do you mean by this? Are there some options that are missing from daytona git-provider add?

[TS35]

Hi @TS35,

We're definitely committed to adding support for any available git providers.

If you're up for it, you can implement it through a PR yourself. You can check implementations for existing providers here.

Alternatively, it would be great if future versions of Daytona could include more customizable options for git-provider, similar to how the Server in Daytona allows for some customization through modifications to the config.json file.

What do you mean by this? Are there some options that are missing from daytona git-provider add?

Thank you for your response. What I meant is that when I tried to use Gitee in Daytona, I selected GitLab Self-managed in the git-provider options. Daytona then prompted me to enter the Self-managed API URL, and I noticed that the provided example was http://gitlab-host/api/v4/, while the API URL provided by Gitee is https://gitee.com/api/v5/. Therefore, I wondered if it would be possible to support Gitee in Daytona through some custom settings. However, I understand that this may not be as simple as the Server in Daytona, where users can achieve it just by making some straightforward changes to the config.json, right? This would likely involve modifying Daytona's source code.

[Tpuljak]

This would likely involve modifying Daytona's source code.

That's true. We need to implement a new git provider (e.g. https://github.com/daytonaio/daytona/blob/main/pkg/gitprovider/azure-devops.go) for the Gitee API. You would then be able to select Gitee in the daytona git-provider add UI.

[Tpuljak]

@quest-bot stash 100

[quest-bot]

New Quest!

A new Quest has been launched in @daytonaio’s repo.
Merge a PR that solves this issue to loot the Quest and earn your reward.

---

Loot of 100 USD has been stashed in this issue to reward the solver!

🗡 Comment @quest-bot embark to check-in for this Quest and start solving the issue. Other solvers will be notified!

⚔️ When you submit a PR, comment @quest-bot loot #1341 to link your PR to this Quest.

Questions? Check out the docs.

---

👉 If no one is assigned to the issue, you are welcome to embark on the quest and tackle it without confirmation from us. In the event that multiple PRs are made from different people, we will generally accept those with the cleanest code.

[katungi]

Hey @Tpuljak , this looks like a good challenge, is anyone working on it?
If not, I can take a swing on it.

[Tpuljak]

@katungi of course, go for it!

[katungi]

@quest-bot embark

[quest-bot]

@katungi has embarked on their Quest. 🗡

• @katungi has been on GitHub since 2017.
• They have merged 32 public PRs in that time.
• Their swords are blessed with JavaScript and TypeScript magic ✨
• They haven't contributed to this repo before.

This is not an assignment to the issue. Please check the repo’s contribution guidelines before submitting a PR.

Questions? Check out the docs.

[naaa760]

@quest-bot embark

[quest-bot]

@naaa760 has embarked on their Quest. 🗡

• @naaa760 has been on GitHub since 2024.
• They have merged 4 public PRs in that time.
• Their swords are blessed with JavaScript and TypeScript magic ✨
• They haven't contributed to this repo before.

This is not an assignment to the issue. Please check the repo’s contribution guidelines before submitting a PR.

Questions? Check out the docs.

[naaa760]

Hello!
I would like to work on this issue!

[Tpuljak]

Hello!

I would like to work on this issue!

Hi @naaa760,

I can see that you're embarking on a lot of issues.

I suggest that you focus on one issue at a time and embark only on those that you're actively working on.

Embarking on an issue doesn't mean that you have the exclusive right to work on it and earn the bounty.