-
Notifications
You must be signed in to change notification settings - Fork 65
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
feat: update contributing guide #288
Conversation
✅ Deploy Preview for docs-open ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
@BekahHW I have a note here. The syntax for the "danger" one is actually Hopefully, updating the Docusaurus in the future will resolve this. I included screenshots of before and after in the PR form. So, if you want me to change the "danger" to what we had previously, please let me know. Thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a couple of things to break up the special notes.
@BekahHW I made the changes here based on your suggestions. One note, I moved the note for maintainer as part of point 9 as below screenshot because it talks about PR form. So, it make more sense to have this note as part of this point. But let me know if you want me to move it back to after the warning (danger) highlight. Thanks! :) |
## [1.70.0](v1.69.0...v1.70.0) (2024-04-04) ### Features * update contributing guide ([#288](#288)) ([1655c76](1655c76))
🎉 This PR is included in version 1.70.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
* fix: update point 1 and 2 to emphasize creating a new branch * feat: add rules for PRs that will be marked as invalid * feat: apply special admonitions syntax * feat: add additional information to a note * fix: move info about DMs to community section * fix: revert info for maintainers to be a quote 1655c76
Description
This PR updates contributing guide with the following changes:
good first issue
.What type of PR is this? (check all applicable)
Related Tickets & Documents
Closes #287
Mobile & Desktop Screenshots/Recordings
Before
After
Steps to QA
Tier (staff will fill in)
[optional] Are there any post-deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?