mu/snapshot_lesson

#!/bin/sh
# Hacky little helper called from edit/ and sandbox/ apps to save a snapshot
# of lesson/ using git.
set -e

test -d lesson/.git || exit 0  # give up if it's not a git repo

cd lesson
# explicitly say '--all' for git 1.9
git add --all .
# bug in git: git diff -q messes up --exit-code
git diff HEAD --exit-code >/dev/null || git commit -a -m . >/dev/null
3789 I accidentally got rid of git snapshotting of lessons back when I switched to testable file primitives last December (commit 3705). >:-( Bringing it back now, hopefully better. The improvement is that there's now at most one commit every time we hit F4. This change adds yet another reason that running `mu` from a different directory is just not supported. 2017-03-12 08:31:55 +00:00			`#!/bin/sh`
			`# Hacky little helper called from edit/ and sandbox/ apps to save a snapshot`
			`# of lesson/ using git.`
4211 Just ran into first issue from using the portable /bin/sh rather than a modern shell: https://stackoverflow.com/questions/15744421/read-command-doesnt-wait-for-input Turn on errexit everywhere. 2018-02-20 09:36:02 +00:00			`set -e`
3789 I accidentally got rid of git snapshotting of lessons back when I switched to testable file primitives last December (commit 3705). >:-( Bringing it back now, hopefully better. The improvement is that there's now at most one commit every time we hit F4. This change adds yet another reason that running `mu` from a different directory is just not supported. 2017-03-12 08:31:55 +00:00
			`test -d lesson/.git \|\| exit 0 # give up if it's not a git repo`

			`cd lesson`
			`# explicitly say '--all' for git 1.9`
			`git add --all .`
			`# bug in git: git diff -q messes up --exit-code`
			`git diff HEAD --exit-code >/dev/null \|\| git commit -a -m . >/dev/null`