Emily Davenport Added caption for Figure 2  over 8 years ago

Commit id: 75a812c1fce0090df510a9a13ba1fb035fa6bf72

deletions | additions      

       

All past commits are located in the hidden \verb|.git| directory in your repository.  \textbf{Figure \ref{fig:Fig2}. Working with a local repository.}  FIXME A) To designate a directory on your computer as a Git repo, type the command \verb|git init|.   This initializes the repository and will allow you to track the files located within that directory.  B) Once you have added a file, follow the git add/commit cycle to place the new file first into the staging area by typing (\verb|git add|) to designate it to be committed, and then \verb|git commit| to take the shapshot of that file.   The commit is assigned a commit identifier (d75es) that can be used in the future to pull up this version or to compare different committed versions of this file.  C) As you continue to add and change files, you should regularly add and commit those changes.   Here, an additional commit was done and the commit log now shows two commit identifiers: d75es (from step B) and f658t (the new commit).  Each commit will generate a unique identifier, which can be examined in reverse chronological order using \verb|git log|.  \textbf{Figure \ref{fig:Fig3}. Working with both a local and remote repository as a single user.}  A) On your computer you commit to a Git repository (commit d75es). 

The original cool\_project still does not have your update to the README file.  F) To suggest the change in the README to the original cool\_project team, submit a pull request via GitHub.  If the owner(s) of the cool\_project repository like your change, they will accept the pull request and your changes will be incorporated into the project.