Skip to content

Conversation

@tedinski
Copy link
Contributor

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

  • Each commit message has a non-empty body, explaining why the change was made
  • [na] Methods or procedures are documented
  • [na] Regression or unit tests are included, or existing tests cover the modified code
  • My PR is restricted to a single feature or bugfix

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.

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
Copy link
Contributor

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?

- [Architecture diagrams]()
- [Code tour]()
- [Testing]()
- [Setting up a dev environment]()
Copy link
Contributor

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?

Copy link
Contributor Author

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? 😁

Copy link
Contributor

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?
Copy link
Contributor

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?

Copy link
Contributor Author

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.

@tedinski tedinski merged commit 805299f into model-checking:main Oct 27, 2021
@tedinski tedinski deleted the doc-cheat-sheets branch October 27, 2021 14:31
@tedinski tedinski mentioned this pull request Nov 10, 2021
12 tasks
tedinski added a commit to tedinski/rmc that referenced this pull request Apr 26, 2022
* Introduce dev command 'cheat sheets'

* edits in response to feedback
tedinski added a commit that referenced this pull request Apr 27, 2022
* Introduce dev command 'cheat sheets'

* edits in response to feedback
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants