-
Notifications
You must be signed in to change notification settings - Fork 4
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
Create text for PR exercise with our book (closes #22). #27
Conversation
* Note: We're especially looking for some more Python-based examples/repositories! | ||
* Identify a resource (website, tutorial, youtube video, etc.) that you find useful that relates to the content of this class. | ||
2. Create a fork of this repository (IBEEM-MSU/ibeem-collaborative-coding) | ||
3. Edit the text of the `10-resources.rmd` file to add in your repository/resouce. |
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.
what do you think about adding a step 1. (optionally) create a branch for your change
? this will also give practice creating and using branches
* Identify a public repository on GitHub that falls into one of the three categories we discussed (package, project, reference). | ||
* Note: We're especially looking for some more Python-based examples/repositories! | ||
* Identify a resource (website, tutorial, youtube video, etc.) that you find useful that relates to the content of this class. | ||
2. Create a fork of this repository (IBEEM-MSU/ibeem-collaborative-coding) |
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.
to get practice creating issues, a participant could create an issue in our repo "examples should include ", then in their commit message they can reference this issue
this is really great! I have 2-3 suggestions to give practice with additional github collab features. I (redundantly) also commented in the code
|
merged via in PR #31, so closing |
No description provided.