Closed idagelic closed 1 week ago
/bounty $30
/attempt #855
with your implementation plan/claim #855
in the PR body to claim the bountyIf 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 |
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>)
Can push a PR if you confirm with above..
@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.
@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
💡 @abhishek818 submitted a pull request that claims the bounty. You can visit your bounty board to reward.
🎉🎈 @abhishek818 has been awarded $30! 🎈🎊
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 titleChoose 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 currentnamespaceId
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