-
Notifications
You must be signed in to change notification settings - Fork 28
feat: update contribution workflow based on guideline generated as comment #251
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
base: main
Are you sure you want to change the base?
feat: update contribution workflow based on guideline generated as comment #251
Conversation
✅ Deploy Preview for scrc-coding-guidelines ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
felix91gr
left a comment
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.
Sorry I'm late. These have been pretty hard weeks.
Anywho. I hope this helps @PLeVasseur
CONTRIBUTING.md
Outdated
| Follow the guidance given in the comment with the guideline on which | ||
| chapter to place the coding guideline. |
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.
I'm not sure what we mean here. What do we mean here? :)
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.
Attempted to clarify in: b012450
Let me know what you think ✌️
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.
https://github.com/rustfoundation/safety-critical-rust-coding-guidelines/blob/b012450a6cdb9de0f03449b1f789ec32c359ca34/CONTRIBUTING.md#4-create-the-pr this is how it's rendered. I'm still a bit lost there
| [6) Contributor Applies Feedback on Issue](#6-contributor-applies-feedback-on-issue) | ||
| and | ||
| [7) Contributor Applies Regenerated Guideline to PR](#7-contributor-applies-regenerated-guideline-to-pr) |
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.
I think these should be sub-steps or perhaps they could be elided? I can check on this again tomorrow, but for today's me, they feel like they're like step 5.2 that got accidentally promoted to main steps :)
8de045b to
72efde1
Compare
Co-authored-by: Félix Fischer <felix91gr@users.noreply.github.com>
Co-authored-by: Félix Fischer <felix91gr@users.noreply.github.com>
Co-authored-by: Félix Fischer <felix91gr@users.noreply.github.com>
Co-authored-by: Félix Fischer <felix91gr@users.noreply.github.com>
Co-authored-by: Félix Fischer <felix91gr@users.noreply.github.com>
Co-authored-by: Félix Fischer <felix91gr@users.noreply.github.com>
closes #224
Example of what the generated guideline looks like:
#246 (comment)