this is for holding javascript data
John Blischak Remove caption for Figure 1 from section text. This was a failed
experiment. It'll be easier to just build a local version for submission
than to try and create one version that will work both online on
Authorea and for PLOS submission. See #23.
over 8 years ago
Commit id: 4a44d33dacbfe760790bff3b1de76a74f570576c
deletions | additions
diff --git a/version-your-code.tex b/version-your-code.tex
index 4e688e9..eebed1f 100644
--- a/version-your-code.tex
+++ b/version-your-code.tex
...
For this reason, projects under version control tend to be stored within a single directory to correspond with a single Git repository.
For strategies on how to best organize your own projects, see Noble, 2009 \cite{19649301}.
\textbf{Figure \ref{fig:Fig1}. The git add/commit process.}
To store a snapshot of changes in your repository, first \verb|git add| any files to the staging area you wish to commit (for example, you've updated the \verb|process.sh| file).
Second, type \verb|git commit| with a message. Only files added to the staging area will be committed.
All past commits are located in the hidden \verb|.git| directory in your repository.
\begin{verbatim}
$ cd ~/thesis
$ ls