-
Notifications
You must be signed in to change notification settings - Fork 63
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
Feature: Add OpenSauced for Contributors Guide #208
Comments
Hey @BekahHW, I'd love to help out with creating this guide, if such an opportunity is available. |
@ATREAY how are things going? |
Hey @BekahHW, Unfortunately, my college has unexpectedly announced exams, and I anticipate being unable to dedicate time to this task for the next week. If it is acceptable, I am committed to working on this issue after the exams are over. I sincerely apologize for any inconvenience this may cause. |
I'll do it @BekahHW |
Thanks for being interested in this issue. It looks like this ticket is already assigned to a contributor. Please communicate with the assigned contributor to confirm the status of the issue. |
Hey @CBID2 we jut merged in the guide for job seekers. SO you might want to take a look at that and the maintainers guide.. Let me know if you have questions. |
You mean look at those two guides as references @BekahHW? |
@CBID2 yep! |
🎉 This issue has been resolved in version 1.65.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Type of feature
🍕 Feature
Current behavior
We currently don't have a clear guide for contributors.
Suggested solution
Following the Maintainers Guide as an example, create a guide for contributors. Try to follow the same sections and headings for consistency.
In addition to the features included in the Maintainers card, also include the dev card.
Additional context
No response
Code of Conduct
Contributing Docs
The text was updated successfully, but these errors were encountered: