John Blischak \label -> \ref for Figure 3 and S1 Figure.  almost 9 years ago

Commit id: 0d51b871c3985b475d51cedad63710fa3f8ee517

deletions | additions      

       

$ git clone https://github.com/scientist123/cool_project.git  \end{lstlisting}  After making the edits you want, you can add, commit, and push the changes back to your remote repository on GitHub (\label{fig:Fig3}). (Figure \ref{fig:Fig3}).  \begin{lstlisting}  $ git add README 

To merge this change into the main repository that is owned by the creator of the software, send a pull request using the GitHub interface (Pull request -\textgreater New pull request -\textgreater Create pull request).  After the pull request is created, the owner of the original repository can review your change.  If she approves of the change, she can merge it into the main repository.  Although this process of forking a project’s repository and issuing a pull request seems like a lot of work to contribute changes, this workflow gives the owner of the project control over what changes get incorporated into the code. You can have others contribute to your projects using the same workflow (\label{fig:S1_Fig}). (Figure \ref{fig:S1_Fig}).  The ability to use Git to contribute changes is very powerful because it allows you to improve the software that is used by many other scientists and also potentially shape the future direction of its development.