You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
87 lines
2.3 KiB
87 lines
2.3 KiB
\documentclass{beamer} |
|
|
|
|
|
\usepackage{pgfpages} |
|
%showNotes%\setbeameroption{show notes on second screen=right} |
|
%\setbeamertemplate{note page}{\pagecolor{yellow!5}\insertnote} |
|
\setbeamertemplate{note page}{\setlength{\parskip}{12pt}\pagecolor{yellow!5}\vfill\insertnote\vfill} |
|
\usepackage{palatino} |
|
\usepackage[utf8]{inputenc} |
|
|
|
\usetheme{default} |
|
\beamertemplatenavigationsymbolsempty |
|
\hypersetup{pdfpagemode=UseNone} % don't show bookmarks on initial view |
|
|
|
\usepackage{graphicx} |
|
\graphicspath{ {./auto-images/} } |
|
|
|
%Information to be included in the title page: |
|
\title{Git} |
|
\author{Jonathan Hodgson (Archie)} |
|
\date{\today} |
|
|
|
|
|
|
|
\begin{document} |
|
|
|
\frame{\titlepage} |
|
|
|
\note{% |
|
A few people recently have asked me about Git. |
|
|
|
Git has become the de-facto for most situations. |
|
|
|
Microsoft recently moved to git for version controlling Windows and Office. |
|
} |
|
|
|
\begin{frame} |
|
\frametitle{Obligitary XKCD Comic} |
|
\begin{center} |
|
\includegraphics[width=\textwidth,height=0.8\textheight,keepaspectratio]{auto-xkcd-1597} |
|
\end{center} |
|
\note{% |
|
Git's interface can seem weird, mainly because it is. I think that understanding a bit about how Git works under the hood helps with understanding why some of the commands do what they do. |
|
} |
|
\end{frame} |
|
|
|
\begin{frame} |
|
\frametitle{Why bother?} |
|
|
|
\begin{itemize} |
|
\item Keep track of source code (or other folders and files) |
|
\item Facilitate collaboration |
|
\end{itemize} |
|
|
|
\note{% |
|
This applies to most (if not all) version control systems. |
|
|
|
It's useful even if you're working on things by your self. This presentation is version controlled. |
|
|
|
You can use it to find out when something broke. I won't be covering it today but there is a tool called git bisect that can take a unit test (or script) to analyse when something broke using a binary search. |
|
} |
|
|
|
\end{frame} |
|
|
|
|
|
\begin{frame} |
|
\frametitle{A bit of theory - Blob} |
|
|
|
In Git, a file is called a blob. |
|
|
|
|
|
|
|
\note{% |
|
This bit is a bit boring but I really think it will help with grasping what git does. |
|
|
|
I think with a lot of tools that we use, having a deep understand of how they work means that we can use them better. |
|
} |
|
\end{frame} |
|
|
|
\begin{frame} |
|
\frametitle{Commits} |
|
\begin{center} |
|
\includegraphics[width=\textwidth,height=0.8\textheight,keepaspectratio]{auto-xkcd-1296} |
|
\end{center} |
|
\end{frame} |
|
|
|
\end{document}
|
|
|