Skip to content

Instantly share code, notes, and snippets.

@ivonne-hernandez

ivonne-hernandez/session3_hw_mod0.md

Forked from ericweissman/session3_hw_mod0.md
Last active July 20, 2021 23:20
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save ivonne-hernandez/bc5fbb056c6a6e717caeb6374576e4eb to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save ivonne-hernandez/bc5fbb056c6a6e717caeb6374576e4eb to your computer and use it in GitHub Desktop.
Download ZIP
Raw
session3_hw_mod0.md

Session 3 HW

CAREFULLY READ ALL THE INSTRUCTIONS BEFORE STARTING THESE EXERCISES!

To start this assignment:

  1. Click the button in the upper right-hand corner that says Fork. This is now your copy of the document.
  2. Click the Edit button when you're ready to start adding your answers.
  3. To save your work, click the green button in the bottom right-hand corner. You can always come back and re-edit your gist.

Readings + Responses

Git + Github Review (20 min)

Read David's article on Git and GitHub

  • Use the article and outside resources (Google!) to describe the general process of a collaborative git workflow in the space below.

The general process of a collaborative git workflow starts with you working on a branch off of the main work project on your work laptop. Once you've made progress and commited it to Git you can push your repo to GitHub. When the work on the branch is complete, a pull request can be opened. Pull requests are used when a developer who is done or has made significant progress on their branch asks other developers to leave feedback or requests for changes. If your pull request is approved, this will allow your branch to merge into the main branch. If your pull request is rejected, this will prevent your branch from merging to the main branch. You and the rest of your team can continue to make changes on your individual branches without affecting the main tree. You'll repeat the pull request process everytime you've made significant changes to your branch that you'd like to merge to the main tree.

Slack Shortcuts and Features (10 min)

Use Google to go find at least one online resource detailing keyboard shortcuts and/or features that are built into Slack.

  • What resource(s) did you find? Paste them below:
  1. https://slack.com/help/articles/201374536-Slack-keyboard-shortcuts
  2. https://www.shortcutfoo.com/app/dojos/slack-mac/cheatsheet

Questions/Comments/Confusions

If you have any questions, comments, or confusions that you would like an instructor to address, list them below:

  • Is there anyway that we can get more time to work on the exercises during class? Sometimes we get stuck or have to search for things in our directories before we're able to implement them into our practice. I usually try to rush through the remainder of the exercise after we've come back together, but it'd be nice to share this with the people in my breakout room. When we do intros, I try to write their names down so that I can still talk to them afterwards but some of them only have their last name initial so my interaction with them unfortunately ends there.
  • Is there anyway that we can have the instructors make their terminal easier to read? At times, some of the letters are cut off or the window takes up a quarter of the screen and it's hard to read. I'll bring this up during our next session, I apologize for not speaking up sooner.

Exercises

Task 1: Practicing Git Workflow and Pushing a Repo to GitHub (20 min)

  1. From your command line, make a directory git_and_gh_practice with two files inside: hobbies.md and travels.md.
  2. Initialize git, add your two files, and make an initial commit.
  3. Use your text editor to open hobbies.md.
  4. Add some text about your hobbies.
  5. Add the changes and commit.
  6. Use your text editor to open travels.md.
  7. Add some text about your favorite vacation or travel experience.
  8. Add the changes and commit.
  9. Add a new file to your directory called motivations.md.
  10. Add some text about what is motivating you to change your career.
  11. Add the changes and commit.
  12. On GitHub, create a new repository.
  13. Add the remote to your local repository.
  14. Push your repository to GitHub.

🍩 TURN THIS INTO A LINK TO YOUR REPOSITORY 🍩

Task 2: Forking a Repo on GitHub and Creating a Pull Request (30 min)

  1. Fork the Mod 0 Resources repository.
  2. Open your terminal
  3. Clone your fork to your computer (git clone <url>).
  4. cd into your cloned repository.
  5. Make a new file with the pattern lastname_firstname_resources.md.
  6. Open the file you just created in your text editor.
  7. Create a list of some of your favorite resources so far related to coding/Turing/git/GitHub/etc. These resources do not need to be ones that we've discussed in class. They can be anything that has helped you so far in your journey to learn software development.
  8. Add your changes.
  9. Commit your changes with a properly formatted commit message.
  10. Push your changes to your fork.

This next part is not something we discussed during class and will involve some figuring out on your own.

  1. Use the site:help.github.com Googling trick to search GitHub's help area to figure out how to create a pull request from a fork. It may also be helpful to figure out what pull request means and do additional research!
  2. Open a pull request for your changes.

Once your pull request is open, you're done! You don't need to submit or paste anything since we will get a notification that you've opened a pull request.

IMPORTANT: Do NOT remove this mod0_student_resources directory. You will be using this directory during the next session.

Self Assess

Using the rubric below, assess how you did with these exercises. These are the same metrics your instructors will use to determine if you are prepared for Mod 1!

  • I read carefully read ALL directions
  • I completed all parts of the exercises (not including Extensions) to the best of my ability
  • I used correct syntax, spacing and naming conventions
  • I followed ALL formatting instructions
  • I pushed myself out of my comfort zone and experimented/broke things to try to learn
  • I spent no longer than 20-30 mins Googling a specific problem before asking for help
  • I went back to the lesson to search for clarification before asking for help

Stuck? Having Issues?

Are you stuck on something? Here is the BEST way to ask for help:

  • Start or reply in the thread with the problem you are facing. Be sure to follow the guidelines for asking questions below:
    • I can explain what I am trying to do or accomplish
    • I can what I have tried so far and/or what resources I've tried online
    • I can describe specifically what I am stuck on
    • I provided screenshots and/or code examples to give context
      • If I provided short code examples, I used inline code formatting for single lines of code/error messages
      • If I provided larger blocks of code, I used a code snippet in the correct format (such as .js or .rb)
  • Usually, your classmates will be able to answer your question or point you in the right direction very quickly! If not, an instructor will reply within 24-48 hours
@corneliusellen
Copy link

corneliusellen commented Jul 20, 2021

@ivonne-hernandez Nice work on this.

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