feat: multi-profile support for git providers(#777)

[the-johnwick]

Support for Multiple Git Provider Tokens and Auto-Selection

Description

This update allows users to add multiple tokens for the same Git provider and specify which token to use with the --git-provider-config-id="..." flag or let the system auto-select the appropriate token.

Key Changes:

1. Git Provider Config Struct:

   • Alias: Token alias for better identification.
   • ProviderId: Git provider name (e.g., GitHub, GitLab).
   • The Git provider ID is now a randomly generated UUID.

2. Project and Project Config:

   • Added GitProviderConfigId field to associate a specific Git provider config with the project or project config.

3. Token Selection Logic:

   • Fetch the repository context; if successful, it uses that token for the project. If an error occurs, it moves to the next token.

Breaking Change:

• The Id of the Git provider config is now a randomly generated UUID.
• ProviderId now represents the Git provider name instead of an identifier.

---

• This change requires a documentation update
• I have made corresponding changes to the documentation

This PR addresses issue #777
/claim #777

[Tpuljak]

@the-johnwick the PR is ready for review but there's nothing in the description and one of the checks is failing.

[the-johnwick]

@Tpuljak yes I already commented the problem #777 (comment)

[Tpuljak]

That comment should go on the PR and not the issue.

Please include a description in the PR before requesting a review. The description should be filled out according to the template and be enough to describe all the changes made in the PR.

[Tpuljak]

Did you run /hack/generate-cli-docs.sh?

[the-johnwick]

@Tpuljak Sure I will add detailed description.

[the-johnwick]

Did you run /hack/generate-cli-docs.sh?

Yes, twice

[Tpuljak]

It really does output a diff for me when running.

Are you maybe developing daytona inside of daytona?

[the-johnwick]

It really does output a diff for me when running.

Are you maybe developing daytona inside of daytona?

@Tpuljak No, I wasn't using Daytona and in last commit those two files were modified but still failling the checks

[Tpuljak]

It really does output a diff for me when running.
Are you maybe developing daytona inside of daytona?

@Tpuljak No, I wasn't using Daytona and in last commit those two files were modified but still failling the checks

Please rerun it and commit (without forcing) separately.

[the-johnwick]

@Tpuljak ok I will try

[the-johnwick]

@Tpuljak No differnce. it is still failing with the same error

[Tpuljak]

@the-johnwick can you please record your screen while running

./hack/generate-cli-docs.sh
git status

[the-johnwick]

./hack/generate-cli-docs.sh

sure i will record

[the-johnwick]

@Tpuljak Please check
https://github.com/user-attachments/assets/45a09f06-af6d-4353-9c77-d0975e55a2de

[Tpuljak]

@Tpuljak Please check https://github.com/user-attachments/assets/45a09f06-af6d-4353-9c77-d0975e55a2de

Thanks for the video. I noticed that you're running this on windows. That's the issue. Please run with GOOS=linux set. The issue is that we exclude some files from the windows build so they're not generated in the docs in your case.

[the-johnwick]

@Tpuljak Please check https://github.com/user-attachments/assets/45a09f06-af6d-4353-9c77-d0975e55a2de

Thanks for the video. I noticed that you're running this on windows. That's the issue. Please run with GOOS=linux set. The issue is that we exclude some files from the windows build so they're not generated in the docs in your case.

I will try it again 🙂

[the-johnwick]

@Tpuljak You check the PR now I have added the description and all checks are passing now.

[the-johnwick]

@Tpuljak You can check the PR now I have resolved the merge conflicts and added the detailed description of the PR

[Tpuljak]

Started with the review but I got a FATAL error when running dtn gp ls.

I had git providers set on the main branch and then switched to yours.

I assume that this branch is a breaking change due to changes in the GitProviderConfig struct.

Please add a breaking change description to the PR and BREAKING CHANGE: <description> above the signoff in the commit (you should squash the commits into one). The description in the PR should include steps on how to act after upgrading, while the description in the commit should only include what "broke".

[the-johnwick]

@Tpuljak Thank you for the review. Could you please share a screenshot of the error so I can better understand what happened? The expected behavior is that it should work perfectly across all branches since the changes I made are branch-independent. Additionally, I believe we don't have separate Git configurations for different branches from the same repository.

[the-johnwick]

Git provider

gp.mp4

Project Config Add

pc.mp4

Project creation

create.mp4

[the-johnwick]

@Tpuljak Can I Spilt this PR in to part since it is big PR and it implements more than one features and it would be easy for you to review as well.

[Tpuljak]

@Tpuljak Can I Spilt this PR in to part since it is big PR and it implements more than one features and it would be easy for you to review as well.

There are more than 180 conversation items here and it's close to done. No need to split this into 2 PRs since it's only one feature that it implements.

[Tpuljak]

Nice work on this. Everything seems to be working as it should now.

Added 3 more small comments that should be addressed and then I can approve.

[Tpuljak]

Nice work!

[idagelic]

Thank you for your time! @the-johnwick