-
Notifications
You must be signed in to change notification settings - Fork 129
Introduce dev command 'cheat sheets' #572
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
Conversation
| So you don't have to worry about a series of "oops typo fix" messages while fixing up your pull request, these can be edited out of the final message when you click merge. | ||
|
|
||
| ```bash | ||
| # Set up your git fork |
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.
Should we mention first creating your own fork on github?
rmc-docs/src/SUMMARY.md
Outdated
| - [Architecture diagrams]() | ||
| - [Code tour]() | ||
| - [Testing]() | ||
| - [Setting up a dev environment]() |
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.
Would this include debugging? If not, can we add a subsection on debugging?
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.
Would you be willing to write that section? 😁
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.
Yes, I can write one with @celinval's help 😃 .
| --set=rust.deny-warnings=false | ||
| ``` | ||
| ```bash | ||
| # Done with that PR, time for a new one? |
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.
Can we add a summary of the steps to submit a 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'm going to separate that out into a different section and PR.
* Introduce dev command 'cheat sheets' * edits in response to feedback
* Introduce dev command 'cheat sheets' * edits in response to feedback
Description of changes:
Introduce an initial set of command build or development commands, to aid our memory and onboarding for new developers.
Also outline some additional developer documentation we should add.
Testing:
How is this change tested?
Is this a refactor change?
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.