daytonaio / daytona

The Open Source Dev Environment Manager.
https://daytona.io
Apache License 2.0
8.11k stars 763 forks source link

Specify filtering parameter in TUI "daytona create" selection steps #855

Closed idagelic closed 1 week ago

idagelic commented 1 month ago

Is your feature request related to a problem? Please describe. When a user runs daytona create with a registered Git provider and selects it - when choosing a namespace there should be a reminder of their choice somewhere in the namespace picker screen. For example, it could be in the title Choose a namespace (GitHub) - but we should realize a better, cleaner location. Same addition is needed in the repository selection screen, there should be a label telling the user about the current namespaceId and during the branch/PR selection a relevant repository label etc.

Describe the solution you'd like The solution cannot make the TUI chunky - suggest an implementation sketch or description first

Additional context This was branched from/suggested in #765

Tpuljak commented 1 month ago

/bounty $30

algora-pbc[bot] commented 1 month ago

💎 $30 bounty • Daytona

Steps to solve:

  1. Start working: Comment /attempt #855 with your implementation plan
  2. Submit work: Create a pull request including /claim #855 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.

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 #862
abhishek818 commented 1 month ago

I guess keeping the parent identifier either in the headers itself OR alongside the no. of items is the best place :

Choose a namespace (GitHub)
Choose a Pull/Merge Request  (<repo-name>)
Choose a Branch (<repo-name>) 

OR,

10 items (Github)    ( "(Github)" to be in a formatted style, something like bold or some font color)
10 items (<repo-name>)
abhishek818 commented 1 month ago

Can push a PR if you confirm with above..

RS-labhub commented 1 month ago

@abhishek818 I guess we don't have to

The solution cannot make the TUI chunky - suggest an implementation sketch or description first

30 usd for this, and further usd for writing the code will be discussed later. 🤣🤣🤣🤣🤣

meanwhile me waiting for new issues.

idagelic commented 1 month ago

@abhishek818 Okay I like the

10 items (Github) ( "(Github)" to be in a formatted style, something like bold or some font color)

option better if you can figure out how to do it cleanly? The issue with adding it to title is that there can be a e.g. "(Project # 2)" suffix in the title already so it would be too much

algora-pbc[bot] commented 1 month ago

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

algora-pbc[bot] commented 1 week ago

🎉🎈 @abhishek818 has been awarded $30! 🎈🎊