You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Git Tutorial.tex
+6Lines changed: 6 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -382,6 +382,12 @@
382
382
\item Creating releases should be done on Github. The main difference is that the tag is generated with a message where you can create a change log from the previous release. Using Github allows you to use Markdown to do so.
383
383
\end{itemize}
384
384
385
+
\section{Intermediate Usage of Git}
386
+
Once you have gotten a grasp of the basic commands of git, there are a few commands that will push your skills a little further. I find myself using most of these commands at least a few times a month.
387
+
388
+
\subsection{Amending Commits}
389
+
Lets say you have just committed some changes and you find that you need to make another small change or fix something that should have been in that last commit. That is when you want to use the \colorbox{light-gray}{\textbf{- -amend}} flag to \colorbox{light-gray}{\textbf{git commit}}. Using this flag allows you to add anything staged to the previous commit you just made. When you commit in this way, the previous commit message will come up again if you want to change it. If not, just write and quit.
390
+
385
391
\section{Using GitHub}
386
392
There are three main reasons to directly go to GitHub instead of using the terminal or your GUI: to make the README, create a release, manage an issue.
0 commit comments