Skip to content

bmcgee23/itmd-361-pp-2017

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

17 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

ITMD 361, Production Problem 01: Cloning and Committing to a Git Repository

For this production problem, you will learn to fork, clone, commit, and then push changes to a remote GitHub repository. Follow the steps below exactly to receive full credit.

  1. While logged into your GitHub account in your web browser, point your browser to https://github.com/profstolley/itmd-361-pp-2017 and click the Fork button. You will then see that you have forked the Production Problems repository from profstolley/itmd-361-pp-2017

    To confirm that you’ve done this correctly, you should see your GitHub account listed on this page once you’ve forked: https://github.com/profstolley/itmd-361-pp-2017/network/members

  2. Once you have forked your own copy of the repository, go to your command line and change to whichever directory that you’ve decided you will keep all of your different Git repositories. I recommend having in your home directory a Projects directory, with subdirectories there for each individual project you have under Git control.

    Clone your copy to your computer by clicking the Clone or download button on GitHub, and copying either the SSH or HTTPS clone address.

    If you choose SSH (preferable), you must have set up your private/public key pair with GitHub. See the instructions for setting up SSH keys with GitHub at https://help.github.com/articles/connecting-to-github-with-ssh/ You’ll then be able to clone this way, using your actual GitHub username where this example says USERNAME:

    $ git clone git@github.com:USERNAME/itmd-361-pp-2017.git

    If you choose HTTPS, you’ll be able to clone the following way, using your actual GitHub username where this example says USERNAME:

    $ git clone https://github.com/USERNAME/itmd-361-pp-2017.git

  3. You can now change directories into itmd-361-pp-2017 and then the pp-01 directory, where you should now have this file, readme.md, on your local computer. Open the file in your editor, and write below the URL to your fork of the GitHub repository, and the add and commit:

    My Production Problems repository URL:https://github.com/bmcgee23/itmd-361-pp-2017

  4. Next, push your commit to GitHub. git push origin master from your command line.

  5. Next, and most crucially, you need to add the instructor’s repository as a second remote. From your command line and within the itmd-361-pp-2017 directory, run the command:

    $ git remote add instructor https://github.com/profstolley/itmd-361-pp-2017.git

    Once you have done that, you can run the command git remote -v and it should list two remotes, one called origin and one called instructor.

    ** To receive all future Production Problems, you will change into your itmd-361-pp-2017 directory and run:**

    $ git pull instructor master

  6. Finally, email the instructor at karl.stolley@gmail.com with the URL for your forked copy of the Production Problems repository, which should be the same URL that you pasted in on line 34 of this file in step 3 above.

    The instructor will then clone your copy of your repository, and update it each week with a git pull, to review your Production Problems.

About

Production Problems for ITMD 361, Fall 2017.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • HTML 59.5%
  • CSS 26.5%
  • JavaScript 14.0%