I decided to spend the day learning github more in depth. One of my favourite resources is GithubImmersion.\nIt can get intimidating to practice your work with a language you never really use (ruby), but I am getting less scared of trying new things and I just created the file to play around with.
\nOne of the most interesting things that I have yet to add to my workflow, is git log\nGetting a listing of what changes have been made is the function of the git log command.
There are a lot of options for selecting which entries are displayed in the log.
\n$ git log --pretty=oneline --max-count=2\n$ git log --pretty=oneline --since='5 minutes ago'\n$ git log --pretty=oneline --until='5 minutes ago'\n$ git log --pretty=oneline --author=<your name>\n$ git log --pretty=oneline --allHere is a great log format that you can use for your own logs:
\n$ git log --pretty=format:'%h %ad | %s%d [%an]' --graph --date=shortIt should output something like this:
\n 6118034 2020-01-31 | added comment (HEAD -> master) [lalawuhan]\n 525466d 2020-01-31 | added a default value [lalawuhan]\n b4cf229 2020-01-31 | Using Argv # [lalawuhan]\n 136ac2f 2020-01-31 | first [lalawuhan]This is what it consists of:
\n--pretty="..." defines the format of the output.%h is the abbreviated hash of the commit%d are any decorations on that commit (e.g. branch heads or tags)%ad is the author date%s is the comment%an is the author name--graph informs git to display the commit tree in an ASCII graph layout--date=short keeps the date format nice and shortBoth gitx (for Macs) and gitk (any platform) are useful in exploring log history.
\ngit status, git add, git commit, and git checkout are such common commands that it is useful to have abbreviations for them.
Add the following to the .gitconfig file in your $HOME directory.
\n.gitconfig\n[alias]\n co = checkout\n ci = commit\n st = status\n br = branch\n hist = log --pretty=format:'%h %ad | %s%d [%an]' --graph --date=short\n type = cat-file -t\n dump = cat-file -p