-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to contribute devcontainer.json to the repo #35
Comments
/bounty $80 |
💎 $80 bounty • DaytonaSteps to solve:
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/content! Add a bounty • Share on socials
|
/attempt #35 Options |
💡 @itsdheerajdp submitted a pull request that claims the bounty. You can visit your bounty board to reward. |
Content Type
Article
Article Description
Write a how-to article to show step by step how dev can create devcontainer.json file and contribute it to the existing repo using the example https://github.com/groq/groq-api-cookbook/
For this to be accepted, PR needs to be created on the groq repo with the valid and working devcontainer and you should follow all of the rules and guides: https://github.com/groq/groq-api-cookbook/blob/main/CONTRIBUTING.md
You will demonstrate in the article creation, contribution and use of a workspace in daytona with one of the cookbook examples.
Target Audience
AI engineer
References/Resources
https://github.com/groq/groq-api-cookbook/blob/main/CONTRIBUTING.md
https://github.com/groq/groq-api-cookbook/
Examples
No response
Special Instructions
No response
The text was updated successfully, but these errors were encountered: