Skip to content

fix(standards): say why the base-SHA fetch failed, not just that it did #166

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
twistedmelonman merged 1 commit into from
Sep 11, 2026
Merged

fix(standards): say why the base-SHA fetch failed, not just that it did #166

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions .github/workflows/standards-check.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -134,11 +134,15 @@ jobs:
exit 0
;;
esac
if git -C repo fetch --depth=1 origin "${BASE_SHA}" 2>/dev/null; then
# Capture stderr rather than discarding it: a fallback that cannot
# say WHY it fired is a rate you can only sample, not a fault you can
# diagnose. Keep it to one line so the annotation stays readable.
if fetch_err=$(git -C repo fetch --depth=1 origin "${BASE_SHA}" 2>&1); then
echo "changed_since=${BASE_SHA}" >> "${GITHUB_OUTPUT}"
echo "scoping to files changed since ${BASE_SHA}"
else
echo "::warning::could not fetch base ${BASE_SHA}; falling back to whole-repo sweep"
fetch_err=$(printf '%s' "${fetch_err}" | tr '\n' ' ' | tr -s ' ')
echo "::warning::could not fetch base ${BASE_SHA}; falling back to whole-repo sweep — git said: ${fetch_err}"
fi

- name: Resolve the standards SHA
Expand Down
Loading