Skip to content
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

Closed
wants to merge 1 commit into from

Conversation

kellykapsar
Copy link
Contributor

No description provided.

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

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

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

@billspat
Copy link
Contributor

this is really great! I have 2-3 suggestions to give practice with additional github collab features. I (redundantly) also commented in the code

  1. creating issue and reference issue number in commit msg
  2. create branch to hold change to as basis of a PR (branching allows the main branch of your fork to stay up-to-date)
  3. including the issue number in the PR description

billspat added a commit that referenced this pull request Apr 16, 2024
also includes merges in PRs for #27 and #29 

Co-authored-by: kellykapsar <kelly.kapsar@gmail.com>
@billspat
Copy link
Contributor

merged via in PR #31, so closing

@billspat billspat closed this Apr 16, 2024
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.

None yet

2 participants