Testing a post-merge hook the hard way

test-post-merge-hook

#!/usr/bin/env bash


patch_file=$(
  curl -L \
    -s \
    https://github.com/transcom/mymove/commit/e22ed5cdd10d7fb46e448c4d99b9d98880279a5a.patch
)

# Checkout a previous branch that doesn't have migration/ changes in it.
git reset --hard 6544b43723fd0e45e9f24046b1f4d98017163e11

# Apply the patch file from above to your local branch to get the script.
echo "${patch_file}" | git apply

# Because we can't go forward in time due to changes in the previous patch,
# we'll need to turn this from a `pre-commit` script to an actual Git hook
# named `post-merge`. The `pre-commit` tooling says it will run based on actual
# Git hooks so it's expected for it to work even though we're not testing
# through the actual `pre-commit` "stages".
mv scripts/check-changes .git/hooks/post-merge
git checkout -- scripts/ .pre-commit-config.yaml

# Pull the latest changes to get to the tip of HEAD and there should be line
# printed at the end that mentions that there have been changes to
# `migrations/`.
git pull --ff-only && rm .git/hooks/post/merge