-
Notifications
You must be signed in to change notification settings - Fork 40
Update contributing guide #247
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
Comments
hi! |
@iambel go for it! |
Love this initiative! ❤ We might as well want to consider having:
Which one to apply is maintainers' call. 👍🏼 Also:
Edit: What I mean by issue form here is the form to submit a bug report and feature request. Adding clarity might be helpful for new (even experienced!) folks in OSS. And it'll make the maintainers' tasks lighter as well.😊 I'll chime in more ideas when I can think more! ✨ |
Hi!I am looking forward to fix this issue if it is still open, thanks! |
Hey @LukysYeep , |
Oh my bad, I did not notice @adiati98 , |
Hey @LukysYeep, If you have some thoughts, you can comment here. |
Thanks all! @iambel @LukysYeep you're always welcome to work on things, no need to ask! Thanks for volunteering to help. Sorry for swooping in and making an update :) I've asked Copilot Agent mode to incorporate the suggestions from here (thanks @adiati98 !) and make updates to the file: #295 |
Oh, so it's already finished? |
Not necessarily - does the contributing guide look clear enough now? It might still need improvements. |
Right now CONTRIBUTING.md could use some more guidance at the top.
Add more of a walkthrough for users, for example:
Also, add contribution guidelines for folks wanting to do minor fixes like typos, or more structural code changes.
The text was updated successfully, but these errors were encountered: