Espen Henriksen
Front-end team lead
Oslo Market Solutions
![](https://s3.amazonaws.com/media-p.slid.es/uploads/728794/images/3915833/me.jpeg)
espen_dev
![](https://s3.amazonaws.com/media-p.slid.es/uploads/728794/images/4949744/Octocat.png)
esphen
Git 301
Advanced Git techniques
![](https://media3.giphy.com/media/cFkiFMDg3iFoI/giphy.gif)
Git can be messy
Improve your toolbox
- If you only know git add, git commit and git merge, this talk is for you
- Git is a massive beast
- Extending your toolbox will pay off in the long run
- Use man pages
- f. ex. git bisect --help
- Ask if you're in trouble!
![](https://media3.giphy.com/media/QNFhOolVeCzPQ2Mx85/giphy.gif)
Inspecting commit history
![](https://s3.amazonaws.com/media-p.slid.es/uploads/728794/images/6096268/2019-05-05-204528_grim.png)
git log --graph
![](https://s3.amazonaws.com/media-p.slid.es/uploads/728794/images/6096271/2019-05-05-204738_grim.png)
git log --stat
![](https://s3.amazonaws.com/media-p.slid.es/uploads/728794/images/6096284/2019-05-05-205350_grim.png)
You can even combine them
git log --stat --graph --oneline
![](https://s3.amazonaws.com/media-p.slid.es/uploads/728794/images/6096416/2019-05-05-215044_grim.png)
Inspect other branches without checking them out
![](https://s3.amazonaws.com/media-p.slid.es/uploads/728794/images/6096280/2019-05-05-205016_grim.png)
git show [<object>...]
![](https://media3.giphy.com/media/8qaq3za7IB7d6/giphy.gif)
Commiting
![](https://imgs.xkcd.com/comics/git_commit_2x.png)
Commits
- Separate subject from body with a blank line
- Limit the subject line to 50 characters
- Capitalize the subject line
- Do not end the subject line with a period
- Use the imperative mood in the subject line
- Wrap the body at 72 characters
- Use the body to explain what and why vs. how
- https://chris.beams.io/posts/git-commit
Summarize changes in around 50 characters or less
More detailed explanatory text, if necessary. Wrap it to about 72
characters or so. In some contexts, the first line is treated as the
subject of the commit and the rest of the text as the body. The
blank line separating the summary from the body is critical (unless
you omit the body entirely); various tools like `log`, `shortlog`
and `rebase` can get confused if you run the two together.
Explain the problem that this commit is solving. Focus on why you
are making this change as opposed to how (the code explains that).
Are there side effects or other unintuitive consequences of this
change? Here's the place to explain them.
Further paragraphs come after blank lines.
- Bullet points are okay, too
- Typically a hyphen or asterisk is used for the bullet, preceded
by a single space, with blank lines in between, but conventions
vary here
If you use an issue tracker, put references to them at the bottom,
like this:
Resolves: #123
See also: #456, #789
![](https://s3.amazonaws.com/media-p.slid.es/uploads/728794/images/6096294/2019-05-05-205931_grim.png)
Git add -p
![](https://s3.amazonaws.com/media-p.slid.es/uploads/728794/images/6096314/2019-05-05-211003_grim.png)
Use a different editor
![](https://media3.giphy.com/media/nvciywp139ebm/giphy.gif)
Reverting merges
![](https://s3.amazonaws.com/media-p.slid.es/uploads/728794/images/6096307/2019-05-05-210814_grim.png)
git revert --mainline
![](https://media2.giphy.com/media/10lNC8dms32Zqw/giphy.gif)
Git cherry-pick
![](https://s3.amazonaws.com/media-p.slid.es/uploads/728794/images/6096420/2019-05-05-215315_grim.png)
Git cherry-pick <commit>...
![](https://media1.giphy.com/media/13kGW3iIy4jQnS/giphy.gif)
Changing history
![](https://s3.amazonaws.com/media-p.slid.es/uploads/728794/images/6096322/2019-05-05-211307_grim.png)
Git rebase master
![](https://s3.amazonaws.com/media-p.slid.es/uploads/728794/images/6096330/2019-05-05-211723_grim.png)
Squashing commits
git rebase -i HEAD~2
![](https://s3.amazonaws.com/media-p.slid.es/uploads/728794/images/6096339/2019-05-05-212035_grim.png)
Squash in a GitLab merge
![](https://s3.amazonaws.com/media-p.slid.es/uploads/728794/images/6096400/gitpushforce.jpg)
Git push --force
![](https://media3.giphy.com/media/cMfvUocLArixO/giphy.gif)
Binary search with bisect
![](https://s3.amazonaws.com/media-p.slid.es/uploads/728794/images/6096344/2019-05-05-212319_grim.png)
Find "Good" commit
![](https://s3.amazonaws.com/media-p.slid.es/uploads/728794/images/6096357/2019-05-05-212820_grim.png)
Start bisecting
![](https://s3.amazonaws.com/media-p.slid.es/uploads/728794/images/6096361/2019-05-05-212909_grim.png)
Test commit, mark as "Good" or "Bad"
![](https://media2.giphy.com/media/10SGQxhDvfIifC/giphy.gif)
Fin
Questions?
https://slides.com/esphen/advanced-git
Advanced Git Techniques
By Eline H
Advanced Git Techniques
- 39