#!/bin/bash

set -e
set -x

script_dir=$(dirname "$0")
# shellcheck source=test/common.sh
source "$script_dir/common.sh"

cd_temp_repo
full_repo=$(pwd)
for i in $(seq 1 10); do
  create_commit
  # Create tags to make git-log decorations for the grafted commit more involved
  git tag -a -m "$i" "tag_$i"
  git perf add -m test-measure 5
done
git perf report -n 5
git perf report -n 20
cd "$(mktemp -d)"
git clone "file://$full_repo" --depth=2 shallow_clone
cd shallow_clone
git perf pull
git perf report -n 2
git perf audit -n 2 -m test-measure
output=$(git perf report -n 3 2>&1 1>/dev/null) && exit 1
if [[ ${output} != *'shallow clone'* ]]; then
  echo "Missing warning for 'shallow clone'"
  echo "$output"
  exit 1
fi
output=$(git perf audit -n 3 -m test-measure 2>&1 1>/dev/null) && exit 1
if [[ ${output} != *'shallow clone'* ]]; then
  echo "Missing warning for 'shallow clone'"
  echo "$output"
  exit 1
fi

# The shallow warning for a PR-branch with a merge as HEAD should be counting the first parent's history.
# This is already the default behavior for git-fetch with the depth option.
cd_temp_repo
full_repo=$(pwd)
for i in $(seq 1 10); do
  create_commit
  git perf add -m test-measure 5
done
git checkout -b feature_branch
for i in $(seq 1 5); do
  create_commit
done
git checkout master
git merge --no-ff -
# Test first-parent fetch-depth behavior even if HEAD is non-merge commit.
commit=$(git rev-parse HEAD)
# Shallow clone with depth == 10 for main branch
cd "$(mktemp -d)"
git init
git remote add origin "file://$full_repo"
# Simulate the behavior of github actions checkout closely
git fetch origin "$commit:local-ref" --depth=10
git checkout local-ref
git perf pull
# Must fail as this expects more history
output=$(git perf report -n 11 2>&1 1>/dev/null) && exit 1
if [[ ${output} != *'shallow clone'* ]]; then
  echo "Missing warning for 'shallow clone'"
  echo "$output"
  exit 1
fi
# Must work as this is the exact history length
# If we erroneously considered the feature_branch's history, it would be filtered
# out and we end up with fewer than 10 commits when following the first parent.
git perf report -n 10

exit 0