This activity is intended to be completed in one week - outside of class preparation work and one class meetings. On our Blackboard course site you were provided with items to read, watch, and do prior to attempting this activity. Do not proceed in this activity until you have minimally:
- Read ISL Section 5.2. The previous link will take you to an online full text pdf from the author’s site. Use the table of contents to quickly navigate the file.
In this repository/directory, you should see five items:
README-img
- a folder containing images that I am embedding within thisREADME.md
file and other files. You do not need to do anything with this..gitignore
- a file that is used to specify what Git can ignore when pushing to GitHub. You do not need to do anything with this.README.md
- the document you are currently reading.bootstrapping
- a folder that contains items for you to complete during the class meeting.
Now, you will make your own copy of this repository.
Read these directions first, then work through them. In this GitHub repo (i.e., my repo):
- Click on the Fork icon near the upper-right-hand corner. You will be taken to a Create a new fork screen.
- Verify that your GitHub username is selected under Owner and
that the Repository name is
activity09-bootstrapping
with a green check mark (this verifies that you do not already have a GitHub repository with this name). - You may provide a Description if you would like. This is a way to provide some additional, more descriptive, meta information related to the things you did. I like to provide a brief description of what happened.
- Verify that Copy the
main
branch only is selected. - Click on the green Create fork button at the bottom of this page.
You should be taken a copy of this repo that is in your GitHub account.
That is, your page title should be username/activity09-bootstrapping
,
where username
is replaced with your GitHub username. Directly below
this, you will see the following message:
forked from gvsu-sta631/activity09-bootstrapping
You will complete the rest of this activity in your forked copy of
the activity09-bootstrapping
repo.
Read these directions first, then work through them. Note that you will be switching between RStudio and your GitHub repo (that you previously forked).
- In RStudio, click on the icon (the icon below the Edit drop-down menu).
- Click on Version Control on the New Project Wizard pop-up.
- Click on Git and you should be on a “Clone Git Repository” page.
- Back to your
activity09-bootstrapping
GitHub repo, click on the green Code button near the top of the page. - Verify that HTTPS is underlined in orange/red on the drop-down menu, then copy the URL provided.
- Back in RStudio, paste the URL in the “Repository URL” text field.
- The “Project directory name” text field should have automatically
populated with
activity09-bootstrapping
. If yours did not (this is usually an issue on Macs),- Click back into the “Repository URL” text field.
- Highlight any bit of this text (it does not seem to matter what or how much).
- Press Ctrl/Cmd and the “Project directory name” should now have
automatically populated with
activity09-bootstrapping
.
- Browse to
STA 631/Activities
(assuming you followed my opinionated file structure from earlier in the semester), then click Choose. - Click on Create Project.
Your screen should refresh and the Files pane should say that you
are currently in your activity09-bootstrapping
folder that currently
has the same files and folders as your GitHub repo. If you are asked for
your GitHub credentials, provide your GitHub username and your PAT (not
your password).
Take a moment to reflect on what is possibly your second time doing this forking process.
- Look back at what you said in Activity 2 (SLR) - hopefully, you wrote this down. What advice would you (now) give past (Week 2-3) you?
Read these directions first, then work through them.
- In your
activity09-bootstrapping
repo folder/directory, locate and click into thebootstrapping
subfolder. - In the
bootstrapping
subfolder, you will be greeted by a newREADME.md
file. Do your best to complete the tasks/directions provide in this subfolder by 11:59 pm (EST) today. - Ask questions in class as you are working. If you need to finish this up outside of our class meetings, remember that you can use our Teams workspace (linked on Blackboard), and post questions/issues in the Muddy channel. If someone else already posted what you though was muddy, add any clarification to their post and give them a “+ 1” 👍. Remember that this space is for conversations as well as posting questions. Read through your peers’ muddy posts and do your best to provide help.
The rest of this README
document contains tasks/directions for the
second class meeting of this week.
This document is based on materials from OpenIntro.
This
work is licensed under a
Creative
Commons Attribution-ShareAlike 4.0 International License.