Skip to content

Add full-history setup step for history-based agent workflows - #165

Merged
strawgate merged 2 commits into
mainfrom
main-0bfe6f0a1dedd41c
Feb 19, 2026
Merged

strawgate merged 2 commits into
mainfrom
main-0bfe6f0a1dedd41c

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Summary

  • Added workflow-definition copies under github/workflows/ for the history-dependent agent workflows:
    • gh-aw-bug-hunter.md
    • gh-aw-docs-drift.md
    • gh-aw-breaking-change-detect.md
    • gh-aw-project-summary.md
  • In each file, inserted an Ensure full history step before Repo-specific setup:
    • checks git rev-parse --is-shallow-repository
    • runs git fetch --unshallow --quiet when shallow

Why

These workflows use git log --since=... in their prompt instructions, so shallow clones can hide relevant commits and reduce detection/report quality.

Validation

  • Ran: make lint-workflows ✅

Note

Per current workflow-editing guardrail in this run, I did not modify .github/workflows/* directly. These copied files under github/workflows/ are ready for a maintainer to relocate into .github/workflows/.

AI generated by Issue Assistant

Add an Ensure full history step to the Bug Hunter, Docs Drift, Breaking Change Detect, and Project Summary workflow definitions copied under github/workflows so maintainers can relocate them into .github/workflows.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@strawgate
strawgate marked this pull request as ready for review February 19, 2026 19:40

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verdict: APPROVE. I found no issues that require changes before merge.


What is this? | From workflow: PR Review Agent

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

@github-actions

Copy link
Copy Markdown
Contributor Author

CI failure is reproducible and comes from generated workflow drift after make compile in Verify compiled workflows.

  • Failing step (job 64200651130): if [ -n "$(git status --porcelain)" ]; then ... exit 1 after compile.
  • Log evidence shows make compile succeeds (Compiled 23 workflow(s): 0 error(s), 0 warning(s)) but leaves many modified/untracked files under .github/workflows/* (including lock files and new trigger-*.yml files), so the lock-file cleanliness check fails.
  • PR #165 currently changes only generated files under .github/workflows/ (4 *.md + 4 *.lock.yml), while source templates under gh-agent-workflows/ are unchanged.

Recommended fix:

  1. Apply the full-history edits to source templates in gh-agent-workflows/*.md (not only .github/workflows/*.md).
  2. Run make compile.
  3. Commit the full generated output under .github/workflows/ (including any trigger/maintenance updates).

Commands run:

  • make compile (exit 0)
  • git status --short immediately after compile (dirty tree with the same workflow/lock changes as CI)
  • git diff --name-only origin/main...HEAD (PR currently touches only 8 generated .github/workflows files)

I did not push a commit because resolving this check requires committing .github/workflows/* generated files, and this automation run is constrained from editing workflow files directly.


What is this? | From workflow: PR Checks Fixer

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.

@strawgate
strawgate merged commit 8b0f9f9 into main Feb 19, 2026
9 of 10 checks passed
@strawgate
strawgate deleted the main-0bfe6f0a1dedd41c branch February 19, 2026 19:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Is Bug Hunter limited to recent commits?

1 participant