A Git Provider should support multiple identities for the same user

Is your feature request related to a problem? Please describe. With reference to discussions in the issue, Users having multiple accounts or multiple access tokens for a git provider (each with their own permissions, access to different organizations and repos) might need the requirement to have the ability to use repos and organizations limited for a specific token. (Can have multiple access tokens within the same account also, ex - separate tokens for public and private repos)

Currently, the command for adding a new git provider just asks for a access token and overrides any existing token (if exists). To move back to previous identity, he/she will need to add back the corresponding token for a git provider. This requires the user to remember the access tokens (last used) for their specific needs. Overall, only a single identity is supported at a time.

Describe the solution you'd like daytona gp add command must ask user to provide unique identity names for each token. And subsequently daytona create command will need the user to input the identity name first.

Describe alternatives you've considered None or N/A

Additional context The implementation plan is open to suggestions, nothing is finalized yet.

Edit: Also includes https://github.com/daytonaio/daytona/issues/777#issuecomment-2230286955

One more thing to consider here: When the user runs daytona create REPO_URL, the server must "auto-select" the appropriate provider identity as well.

💎 $300 bounty • Daytona

Steps to solve:

Start working: Comment /attempt #777 with your implementation plan
Submit work: Create a pull request including /claim #777 in the PR body to claim the bounty
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.

Please respect others by working on PRs that you are allowed to submit attempts to.

e.g. If you reached the limit of active attempts, please wait for the ability to do so before submitting a new PR.

If you can not submit an attempt, you will not receive your payout.

Thank you for contributing to daytonaio/daytona!

Add a bounty • Share on socials

Attempt	Started (GMT+0)	Solution
🔴 @abhishek818	Jul 17, 2024, 11:56:36 AM	WIP
🟢 @onyedikachi-david	Aug 8, 2024, 11:32:00 AM	WIP
🟢 @the-johnwick	Aug 15, 2024, 5:24:06 PM	#1032

Can you assign me this since i have created the issue and totally understand it!

/attempt #777

Algora profile	Completed bounties	Tech	Active attempts	Options
@abhishek818	5 daytonaio bounties + 8 bounties from 5 projects	JavaScript, TypeScript	﹟727	Cancel attempt

Since there is almost no work left on my remaining PRs and couple got completed, Can i take a crack at this?

@abhishek818 have at it 😄

@abhishek818 are you currently working on this ?

I need to get my hands to work 😞 my system is faulty as from Monday I finish it all 💪🏽😌

/attempt #777

Algora profile	Completed bounties	Tech	Active attempts	Options
@onyedikachi-david	5 bounties from 2 projects	JavaScript, Shell		Cancel attempt

Hey @abhishek818, are you still working on this issue? I've completed most of the work on this issue, and if you're okay with it, I can go ahead and raise a PR to help resolve it. Let me know what you think!

@the-johnwick sure go ahead, removing my assignment. Sorry to all others if they have been waiting due to me, it's just things are going bad on my side recently...

@abhishek818 No worries at all, it's totally understandable. If there's anything I can do to help out or if you need support with anything else, just let me know. Take care, and I hope things get better for you soon!

I'll leave the issue unassigned for now since we have a draft PR up and @the-johnwick is close to submitting the PR as well.

We'll assign someone once we have a chance to do an initial review

PR closed accidentally i am still working on it.

PR closed accidentally i am still working on it.

I can't reopen it because your branch contains no new changes. Btw, it will be much easier to work if you open a PR from another branch in your repo, not main.

I will reopen the PR from different branch

/attempt #777

Algora profile	Completed bounties	Tech	Active attempts	Options
@the-johnwick	1 daytonaio bounty + 1 bounty from 1 project			Cancel attempt

@Tpuljak Submitted the PR but checks are filling I tried ran docs generation and still it is failling

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

daytonaio / daytona

A Git Provider should support multiple identities for the same user #777

💎 $300 bounty • Daytona

Steps to solve: