Changed to report class, changed margins and page size

git-primer.tex

@@ -1,4 +1,4 @@
-\documentclass[twoside]{article}
+\documentclass[twoside]{report}
 
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 %% Packages %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
@@ -31,6 +31,9 @@
 \usepackage[]{FiraSans} % sans-serif font; https://tug.org/FontCatalogue/firasansregular
 \usepackage[]{footmisc}
 
+%\usepackage{showframe}
+%\renewcommand*\ShowFrameColor{\color{red}}
+
 
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 %% Commands %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
@@ -45,13 +48,16 @@
 
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 %% Document Setup%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-%\usepackage{geometry}
-%\geometry{
-%	paperheight=8.5in,
-%	paperwidth=5.5in,
-%	heightrounded,
-%	margin=0.5in
-%}
+\usepackage{geometry}
+\geometry{
+	paperheight=11in,
+	paperwidth=8.26in,
+	heightrounded,
+	inner=1.75in,
+	outer=1.50in,
+	textheight=9.00in,
+	top=1.00in,
+}
 
 %\addtolength{\topmargin}{0.4in} % Adjust and bottom margin
 %\addtolength{\textheight}{-0.75in} % Adjust the bottom margin
@@ -140,7 +146,7 @@ All contents  \copyright2024 Kenneth John Odle
 
 \tableofcontents
 
-\newpage
+\chapter{Introduction}
 
 Git is version control software. That is, it allows you to record and track changes to a set of files over time. You can then compare different revisions or even revert some files or the entire project back to a previous version. 
 
@@ -174,7 +180,7 @@ In general, I advise against using any type of GUI with Git. For one thing, Git
 
 A GUI can also obscure what Git is actually doing, meaning that you might end up with less understanding of Git than you would by working on the command line.
 
-\section{Local Repositories}
+\chapter{Local Repositories}
 
 Let's start with local repositories. Assuming you have a folder full of files you want to track using Git, open a terminal window in that location (which is now called your ``working directory'') and type \texttt{git init}. Congratulations! You now have a local Git repo!
 
@@ -188,7 +194,7 @@ Now that you've added your files, they are considered to be \textit{staged}, whi
 
 If you're happy with the files you've staged, we can now commit them by using \texttt{git commit -m "<commit message>"}. Note that you have to add a commit message. This can be anything you like, but it helps to make it something that will be useful down the road like ``updated chapter three''. You'll get some miscellaneous messages about what Git is doing and then it is done. You've created your first commit, and all of your staged files are now \texttt{committed}.\footnote{You can also make this process even more efficient by creating some bash alias for the various Git commands. See ``More Fun with bash'' in issue \#4.}
 
-\section{Branches}
+\chapter{Branches}
 
 If you want to experiment, the best way to do that is to create a \textit{branch}. To do that, just use \texttt{git branch <name>}. To move to that branch, you check it out\footnote{For a visual depiction, see, \kref{https://www.youtube.com/watch?v=8qxDBiiVjlQ}{https://www.youtube.com/watch?v=8qxDBiiVjlQ}.} using \texttt{git branch checkout <branchname>}.
 
@@ -206,11 +212,11 @@ It's always a good idea to clean up after ourselves. If we don't need that exper
 
 In reality, things are rarely going to be this simple, unless you are only making very basic changes to a branch. You'll likely get all sorts of error messages or warning messages, and will get confused or even scared. Never fear! The nice thing about Git is that most of the solutions you need are easily found at the other end of a web search. 
 
-\section{Remote Repositories}
+\chapter{Remote Repositories}
 
 Remote repositories make it possible to share your work and to collaborate with others. You can do all sorts of things locally, but at some point, you're probably going to want to put your work out there, or just to show off.
 
-\subsection{Getting a Remote Repository}
+\section{Getting a Remote Repository}
 
 If you set up a remote repo on some place like GitHub, or you find a repo somewhere that you would like to work with on your own, you can \textit{clone} that remote repo like this:
 
@@ -265,7 +271,7 @@ Running \texttt{git branch} again confirms that our branch has been renamed:
 * main
 \end{Verbatim}
 
-\subsection{Pushing Changes to a Remote Repository}
+\section{Pushing Changes to a Remote Repository}
 
 Okay, I have a local repository, I have a remote repository attached to that local repository, and the current branch on both repos have the same name. It's time to move that code from the local repository to the remote one. For that I'll use \texttt{git push} <name of remote repo> <name of current branch>. Since the remote is named ``ogit'' and the branch is named ``main'', the full command looks like this:
 
@@ -294,7 +300,7 @@ For what it's worth, you can have multiple remotes. I can create a remote reposi
 
 There is a lot more to it than this (I haven't even talked about \texttt{git status} yet!), so I guess I will leave that for part 2 of this primer.
 
-\subsection{Collaborating With Yourself}
+\chapter{Collaborating With Yourself}
 
 I mentioned earlier that you could use Git if you're a writer to keep track of changes to projects, provided you were willing to work with text files. My goal here is to provide at least one workflow for doing that. I'm going to assume a few things:
 
@@ -320,6 +326,8 @@ What does \texttt{git pull} do? It's a combination of two Git commands: \texttt{
 
 \texttt{git fetch} gets the change history of the tracked remote and branch, whereas \texttt{git merge} combines the current branch with the specified branch. My local repository will now look like My remote repository. I can write to my heart's content, push those changes, and call it a day. If I'm back at the hospital waiting room again some time later, I can just repeat the process.\footnote{Again, for a visual depiction of this, please visit \kref{https://www.youtube.com/watch?v=FG1NrQYXjLU}{https://www.youtube.com/watch?v=\\FG1NrQYXjLU}.}
 
+\chapter{Other Things}
+
 \section{Extra Files}
 
 If you pull or clone a remote repository, you may notice files like \texttt{.gitignore} and \texttt{README.md}. The first tells Git which files to \textit{not} track. (And yes, you will want to make use of this at some point.) The second is a text document written in Markdown (hence the \texttt{.md} file extension) which appears on the front page of the online repo.
@@ -330,7 +338,7 @@ These things aren't a part of Git, but they are something that is offered by Git
 
 To \textit{fork} a remote repository is to make a copy of it so that you can contribute to this project. You fork somebody else's project, clone it locally, make your changes, push those changes to your remote repo, and then make a \textit{pull request}, which alerts the owner of the original repository that you have changes you'd like them to incorporate into their project. They can then pull those changes in, or they can ignore them. 
 
-\section{Summary of Git Commands}
+\chapter{Summary of Git Commands}
 
 One of my favorite aspects of Git is that it's fairly intuitive to understand and start using right out of the box, but it's also robust enough to meet the needs of large teams and organizations. What I've done in the following table is to summarize the commands I've used in this primer, along with examples where appropriate.