git-scaffold 0.1.1

Corrected

• surface non-override materialization errors in repatch (87a300c)

Install

With Go on the machine, one command installs this release:

go install github.com/stephenc/git-scaffold@v0.1.1

Or take the file for your machine, and put it where your shell finds it.
On Linux and macOS:

dir=$(mktemp -d) &&
archive="git-scaffold-$(uname -s)-$(uname -m).tar.gz" &&
curl -fsSL -o "$dir/$archive" \
  "https://github.com/stephenc/git-scaffold/releases/download/v0.1.1/$archive" &&
curl -fsSL -o "$dir/$archive.sha256" \
  "https://github.com/stephenc/git-scaffold/releases/download/v0.1.1/$archive.sha256" &&
if command -v sha256sum >/dev/null
then (cd "$dir" && sha256sum -c "$archive.sha256")
else (cd "$dir" && shasum -a 256 -c "$archive.sha256")
fi &&
tar -xzf "$dir/$archive" -C "$dir" git-scaffold &&
mkdir -p ~/.local/bin &&
install -m 755 "$dir/git-scaffold" ~/.local/bin/git-scaffold
[ -n "$dir" ] && rm -rf "$dir"
command -v git-scaffold

These commands write into a temporary directory, and they do not write into
the directory that you are in. The two curl lines take the archive and the
.sha256 file that the release holds beside it. The check compares the two.
The && after each write means a line that fails stops the writes that follow.
The rm line still runs, and it removes the temporary directory.

mkdir makes ~/.local/bin when that directory is not there. install puts
git-scaffold in that directory, and it REPLACES a git-scaffold that is already there.

install does not put ~/.local/bin on your path. command -v git-scaffold must
show a file in ~/.local/bin. If it shows nothing, add ~/.local/bin to the
path of this shell. If it shows a different file, that file is the one the
shell will run.

On Windows, take git-scaffold-Windows-x86_64.zip (or git-scaffold-Windows-arm64.zip for
an ARM machine), check it against the .sha256 file beside it, and put the
git-scaffold.exe that it holds in a directory on your PATH.

The binaries hold no dynamic library, so each one runs on any machine of its
system and architecture. Every command needs git on the path.

Each change: v0.1.0...v0.1.1

git-scaffold 0.1.0

New

• add repatch command and prefer json-patch when adopting files (1b5259d)

Install

With Go on the machine, one command installs this release:

go install github.com/stephenc/git-scaffold@v0.1.0

Or take the file for your machine, and put it where your shell finds it.
On Linux and macOS:

dir=$(mktemp -d) &&
archive="git-scaffold-$(uname -s)-$(uname -m).tar.gz" &&
curl -fsSL -o "$dir/$archive" \
  "https://github.com/stephenc/git-scaffold/releases/download/v0.1.0/$archive" &&
curl -fsSL -o "$dir/$archive.sha256" \
  "https://github.com/stephenc/git-scaffold/releases/download/v0.1.0/$archive.sha256" &&
if command -v sha256sum >/dev/null
then (cd "$dir" && sha256sum -c "$archive.sha256")
else (cd "$dir" && shasum -a 256 -c "$archive.sha256")
fi &&
tar -xzf "$dir/$archive" -C "$dir" git-scaffold &&
mkdir -p ~/.local/bin &&
install -m 755 "$dir/git-scaffold" ~/.local/bin/git-scaffold
[ -n "$dir" ] && rm -rf "$dir"
command -v git-scaffold

These commands write into a temporary directory, and they do not write into
the directory that you are in. The two curl lines take the archive and the
.sha256 file that the release holds beside it. The check compares the two.
The && after each write means a line that fails stops the writes that follow.
The rm line still runs, and it removes the temporary directory.

mkdir makes ~/.local/bin when that directory is not there. install puts
git-scaffold in that directory, and it REPLACES a git-scaffold that is already there.

install does not put ~/.local/bin on your path. command -v git-scaffold must
show a file in ~/.local/bin. If it shows nothing, add ~/.local/bin to the
path of this shell. If it shows a different file, that file is the one the
shell will run.

On Windows, take git-scaffold-Windows-x86_64.zip (or git-scaffold-Windows-arm64.zip for
an ARM machine), check it against the .sha256 file beside it, and put the
git-scaffold.exe that it holds in a directory on your PATH.

The binaries hold no dynamic library, so each one runs on any machine of its
system and architecture. Every command needs git on the path.

Each change: v0.0.1...v0.1.0

git-scaffold 0.0.1

Install

With Go on the machine, one command installs this release:

go install github.com/stephenc/git-scaffold@v0.0.1

Or take the file for your machine, and put it where your shell finds it.
On Linux and macOS:

dir=$(mktemp -d) &&
archive="git-scaffold-$(uname -s)-$(uname -m).tar.gz" &&
curl -fsSL -o "$dir/$archive" \
  "https://github.com/stephenc/git-scaffold/releases/download/v0.0.1/$archive" &&
curl -fsSL -o "$dir/$archive.sha256" \
  "https://github.com/stephenc/git-scaffold/releases/download/v0.0.1/$archive.sha256" &&
if command -v sha256sum >/dev/null
then (cd "$dir" && sha256sum -c "$archive.sha256")
else (cd "$dir" && shasum -a 256 -c "$archive.sha256")
fi &&
tar -xzf "$dir/$archive" -C "$dir" git-scaffold &&
mkdir -p ~/.local/bin &&
install -m 755 "$dir/git-scaffold" ~/.local/bin/git-scaffold
[ -n "$dir" ] && rm -rf "$dir"
command -v git-scaffold

These commands write into a temporary directory, and they do not write into
the directory that you are in. The two curl lines take the archive and the
.sha256 file that the release holds beside it. The check compares the two.
The && after each write means a line that fails stops the writes that follow.
The rm line still runs, and it removes the temporary directory.

mkdir makes ~/.local/bin when that directory is not there. install puts
git-scaffold in that directory, and it REPLACES a git-scaffold that is already there.

install does not put ~/.local/bin on your path. command -v git-scaffold must
show a file in ~/.local/bin. If it shows nothing, add ~/.local/bin to the
path of this shell. If it shows a different file, that file is the one the
shell will run.

On Windows, take git-scaffold-Windows-x86_64.zip (or git-scaffold-Windows-arm64.zip for
an ARM machine), check it against the .sha256 file beside it, and put the
git-scaffold.exe that it holds in a directory on your PATH.

The binaries hold no dynamic library, so each one runs on any machine of its
system and architecture. Every command needs git on the path.