Remove git fetch --unshallow when fixed upstream #224

Activity

1. github-actions commented on Feb 20, 2026

   

   github-actionsBot

   on Feb 20, 2026 – with GitHub Actions

   Contributor

   More actions

   TL;DR: don’t remove git fetch --unshallow yet—upstream github/gh-aw#16896 is still open with no linked PR, and this repo still depends on the workaround in 6 workflow sources (and compiled lock files).

   Recommendation

   Keep the workaround in place for now. Remove it only after upgrading to a gh-aw version that supports configurable checkout depth (or otherwise guarantees full history for these workflows), then regenerate lock files and verify the Ensure full history steps are gone.

   Findings

   • Upstream tracking issue is still open: github/gh-aw#16896 (state: open), and no matching PR was found in github/gh-aw for 16896.
   • Upstream maintainer comment indicates it is still being worked on (“looking into controlling which repo checkout happens so I can also add fetch depth”).
   • Local workflow sources currently containing the workaround:
     • .github/workflows/gh-aw-bug-hunter.md:67-71
     • .github/workflows/gh-aw-breaking-change-detect.md:67-71
     • .github/workflows/gh-aw-docs-drift.md:72-76
     • .github/workflows/gh-aw-project-summary.md:67-71
     • .github/workflows/gh-aw-performance-profiler.md:68-72
     • .github/workflows/gh-aw-docs-drift-external.md:81-85
   • Compiled lock files also contain the same step (e.g. .github/workflows/gh-aw-bug-hunter.lock.yml:558-562, .github/workflows/gh-aw-docs-drift.lock.yml:566-570).
   • The compiler tool version in this repo is pinned at Makefile:4 (GH_AW_VERSION := v0.45.1).

   Verification

   I ran commands to verify the current checkout behavior and workaround effect:

   $ git --no-pager rev-parse --is-shallow-repository && git --no-pager rev-list --count HEAD
   true
   1
   
   $ git --no-pager fetch --unshallow --quiet && git --no-pager rev-parse --is-shallow-repository && git --no-pager rev-list --count HEAD
   false
   162

   This confirms the workaround is currently functional and still relevant in this environment.

   Detailed Action Plan

   1. Track upstream github/gh-aw#16896 until it is closed by an implementation that exposes checkout depth control (or changes default behavior appropriately).
   2. Upgrade GH_AW_VERSION in Makefile:4 to a release that includes that upstream fix.
   3. Regenerate compiled workflows (make compile) so .lock.yml files reflect the new compiler behavior.
   4. Remove Ensure full history steps from the 6 source workflows listed above if they are no longer needed under the new compiler behavior.
   5. Re-run make lint-workflows and verify no git fetch --unshallow --quiet remains in .github/workflows/*.md and .github/workflows/*.lock.yml.
   6. In PR validation, confirm history-based prompts still see expected commit ranges without the workaround.

   Related Items

   Type	Link	Relevance
   Issue	github/gh-aw#16896	Upstream fix tracking for checkout depth customization
   PR	#165	Introduced workaround in history-based workflows
   Issue	#158	Original report that led to workaround
   File	.github/workflows/gh-aw-bug-hunter.md:67-71	Workaround step in source workflow
   File	.github/workflows/gh-aw-docs-drift-external.md:81-85	Additional source workflow using same workaround
   File	.github/workflows/gh-aw-bug-hunter.lock.yml:558-562	Workaround propagated in compiled workflow
   File	Makefile:4	gh-aw compiler version pin

   ---

   What is this? | From workflow: Issue Triage Agent

   Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not. for issue #224
2. strawgate

   added

   pending-upstream

   on Feb 20, 2026