Brendan Dawes

Analogue + Digital


Using a Git Repo to create a physical document of the work

I've always felt it important to document the work. Sketches, scraps, iterations, failures and surprises are all part of the process and so I try and capture those things in the work that I create every day.

None more so than on client work. All my work is tracked through a Git repository β€” a way to track code changes over time, complete with comments on why something has changed or what that commit was about. In conjunction with that I take timestamped screenshots. These two things combined β€” words and image β€” have the side-effect of creating a document of the making process.

So with that in mind I have begun to take those words and images and compile them chronologically into small books, both for myself and the client, as an historical record of how something went from A to B. These books are nothing fancy from a print point of view, being printed online by Blurb, but they serve as permanent physical souvenirs of a process that is often easily forgotten.

To get a line by line tab separated output of any Git repo you can write this in the command line

git log --reverse --date=local --pretty=format:"%h%x09%an%x09%ad%x09%s" > commits.local.tsv

This example shows the book I created for Fermata The front cover features a visualisation of the commits over the course of the project, almost resembling a musical score.

2018-02-08-16.57.47-a8082323937264c2f0d8b18ea3517911 2018-02-08-16.58.13-84a2cca4b4565f10dc70c6ecabd973be 2018-02-08-16.58.22-f783ceab0f8b6fbfa0a3ef84ff2ef5f5 2018-02-08-16.58.49-779e7695e3bd04cd7c39c6c7e2e5897c 2018-02-08-16.59.02-30c1b6aaf61b9b1f4a0b6d4e4a09d396 2018-02-08-16.59.25-551d11cb96a6b7ab25a4ef206a902172 2018-02-08-17.00.30-bfbb8e56c8b21f3ef31af06cb89165bc