Skip to content

Set explicit supported Copilot model for GitHub Guard Coverage Checker#7699

Merged
lpcox merged 2 commits into
mainfrom
copilot/fix-github-guard-coverage-checker
Jun 18, 2026
Merged

Set explicit supported Copilot model for GitHub Guard Coverage Checker#7699
lpcox merged 2 commits into
mainfrom
copilot/fix-github-guard-coverage-checker

Conversation

Copilot AI commented Jun 18, 2026

Copy link
Copy Markdown
Contributor

The scheduled GitHub Guard Coverage Checker (MCP + CLI) workflow was failing in the agent step due to an unsupported model configuration (400 The requested model is not supported). This change pins the workflow to a supported Copilot model to prevent non-transient model-selection failures.

  • Workflow frontmatter update

    • Converted engine config from scalar to explicit object in .github/workflows/github-mcp-guard-coverage-checker.md.
    • Pinned model to gpt-5.4 for deterministic model selection.
  • Compiled lock alignment

    • Updated .github/workflows/github-mcp-guard-coverage-checker.lock.yml to match the source workflow change:
      • GH_AW_INFO_MODEL: gpt-5.4
      • COPILOT_MODEL: gpt-5.4
      • refreshed frontmatter_hash metadata to stay in sync with the .md workflow.

Example of the effective source change:

engine:
  id: copilot
  model: gpt-5.4

GitHub Advanced Security started work on behalf of lpcox June 18, 2026 00:47 View session
GitHub Advanced Security finished work on behalf of lpcox June 18, 2026 00:48
Copilot AI changed the title [WIP] Fix GitHub Guard Coverage Checker model configuration Set explicit supported Copilot model for GitHub Guard Coverage Checker Jun 18, 2026
Copilot finished work on behalf of lpcox June 18, 2026 01:00
Copilot AI requested a review from lpcox June 18, 2026 01:00
GitHub Advanced Security started work on behalf of lpcox June 18, 2026 01:02 View session
GitHub Advanced Security finished work on behalf of lpcox June 18, 2026 01:03
@lpcox lpcox marked this pull request as ready for review June 18, 2026 01:07
Copilot AI review requested due to automatic review settings June 18, 2026 01:07

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

✅ Ready to approve

The change is narrowly scoped to workflow configuration, is internally consistent across source + lock, and directly addresses the reported non-transient model-selection failure.

Note: this review does not count toward required approvals for merging.

Pull request overview

This PR fixes the scheduled GitHub Guard Coverage Checker (MCP + CLI) workflow’s agent step failing due to unsupported/invalid model selection by pinning the workflow to a known supported Copilot model.

Changes:

  • Updated the workflow frontmatter to use an explicit engine object and set model: gpt-5.4.
  • Updated the compiled lock workflow to align with the frontmatter change, including setting GH_AW_INFO_MODEL and COPILOT_MODEL to gpt-5.4 and refreshing the frontmatter_hash.
File summaries
File Description
.github/workflows/github-mcp-guard-coverage-checker.md Switches engine from scalar to object and pins the Copilot model to gpt-5.4 in source frontmatter.
.github/workflows/github-mcp-guard-coverage-checker.lock.yml Aligns the compiled workflow with the pinned model by setting runtime env vars to gpt-5.4 and updating metadata hashes.

Copilot's findings

  • Files reviewed: 2/2 changed files
  • Comments generated: 0

Note

Your feedback helps us improve the quality of this feature.
Please use 👍 or 👎 to tell us whether this assessment is correct.


💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@lpcox lpcox merged commit b5cef02 into main Jun 18, 2026
40 checks passed
@lpcox lpcox deleted the copilot/fix-github-guard-coverage-checker branch June 18, 2026 01:11
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.

3 participants