Is Bug Hunter limited to recent commits? #158

Activity

1. github-actions commented on Feb 19, 2026

   

   github-actionsBot

   on Feb 19, 2026 – with GitHub Actions

   Contributor

   More actions

   Yes — the Bug Hunter prompt explicitly tells the agent to review only the last 14 days of commits, so the workflow is scoped to recent changes unless you update that instruction.

   Recommendation
   If you want Bug Hunter to consider a longer history, change the lookback in .github/workflows/gh-aw-bug-hunter.md (or add a configurable input) and recompile the lockfile.

   Findings

   The Bug Hunter workflow prompt explicitly instructs a 14‑day commit review window:

   .github/workflows/gh-aw-bug-hunter.md:78-83
   78. 1. Review recent changes:
   79.    - Run `git log --since="14 days ago" --stat` and identify candidates with user-facing impact.
   80.    - Read the diffs and related files for each candidate.

   No other instructions in this workflow expand the commit search window beyond that initial 14‑day scan.

   Verification

   No commands were run; this is a configuration/prompt question.

   Detailed Action Plan

   1. Update .github/workflows/gh-aw-bug-hunter.md:78-83 to widen the lookback (for example, 30/90 days) or add a new workflow input (e.g., lookback-days) and reference it in the prompt.
   2. Run make compile to regenerate .github/workflows/gh-aw-bug-hunter.lock.yml.
   3. If you add an input, document it in gh-agent-workflows/bug-hunter/README.md.

   Related Items

   Type	Link	Relevance
   PR	#79	Introduced bug-hunter scheduled report workflow
   PR	#90	Updated Bug Hunter prompt guidance
   Issue	#77	Bug Hunter tracking issue
   File	.github/workflows/gh-aw-bug-hunter.md:78-83	14-day commit review instruction

   ---

   What is this? | From workflow: Issue Triage Agent

   Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not. for issue #158
2. strawgate commented on Feb 19, 2026

   

   strawgate

   on Feb 19, 2026

   ContributorAuthor

   More actions

   /ai can you confirm that git fetch --unshallow works for you? if so let's add unshallow as a step to the frontmatter?

   👀React with 👀1Reacted by github-actions
3. github-actions commented on Feb 19, 2026

   

   github-actionsBot

   on Feb 19, 2026 – with GitHub Actions

   Contributor

   More actions

   Confirmed: in this checkout git fetch --unshallow --quiet succeeds (exit 0) and flips git rev-parse --is-shallow-repository from true to false.

   Suggested frontmatter addition in .github/workflows/gh-aw-bug-hunter.md before the current Repo-specific setup step (lines 66-71):

     - name: Ensure full history
       run: |
         if git rev-parse --is-shallow-repository | grep -q true; then
           git fetch --unshallow --quiet
         fi

   ---

   What is this? | From workflow: Issue Assistant

   Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not. for issue #158
4. strawgate commented on Feb 19, 2026

   

   strawgate

   on Feb 19, 2026

   ContributorAuthor

   More actions

   /ai can you add the step to any workflows that will need the full history?

   👀React with 👀1Reacted by github-actions
5. strawgate commented on Feb 19, 2026

   

   strawgate

   on Feb 19, 2026

   ContributorAuthor

   More actions

   /ai can you add the step to any workflows that will need the full history?

   👀React with 👀1Reacted by github-actions
6. github-actions commented on Feb 19, 2026

   

   github-actionsBot

   on Feb 19, 2026 – with GitHub Actions

   Contributor

   More actions

   Done — I added an Ensure full history step to each workflow that relies on git log --since=...:

   • github/workflows/gh-aw-bug-hunter.md:67
   • github/workflows/gh-aw-docs-drift.md:67
   • github/workflows/gh-aw-breaking-change-detect.md:67
   • github/workflows/gh-aw-project-summary.md:67

   Each now runs:

   - name: Ensure full history
     run: |
       if git rev-parse --is-shallow-repository | grep -q true; then
         git fetch --unshallow --quiet
       fi

   before Repo-specific setup, so history-based scans can see the full commit range.

   Validation run: make lint-workflows (pass).

   I also opened a PR with these changes; because this run is not allowed to edit .github/workflows/ directly, the updated workflow-definition copies are under github/workflows/ for maintainer relocation.

   ---

   What is this? | From workflow: Issue Assistant

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

   closed this as completedin #165on Feb 19, 2026