Skip to content

Clarify conditional gh-aw maintenance workflow checks - #38

Closed
Marco Olivo (olivomarco) with Copilot wants to merge 2 commits into
mainfrom
copilot/platform-assessment-2026-10-gh-aw-drift-sentinel-f
Closed

Marco Olivo (olivomarco) with Copilot wants to merge 2 commits into
mainfrom
copilot/platform-assessment-2026-10-gh-aw-drift-sentinel-f

Conversation

Copilot AI commented Oct 1, 2026 •

Copy link
Copy Markdown
Contributor

Drift Sentinel treated agentics-maintenance.yml as required, though gh-aw generates it only when expiration or no-op issue reporting is enabled. The six workflow locks already use gh-aw v0.90.1.

  • Prompt: Check for the maintenance workflow only when its trigger settings require it.
  • Lock: Regenerate the drift-sentinel lock.

For example, noop.report-as-issue: false does not trigger maintenance workflow generation.

Co-authored-by: olivomarco <8478776+olivomarco@users.noreply.github.com>
Copilot AI changed the title [WIP] Update lock files and assess compiler/runtime discrepancies Clarify conditional gh-aw maintenance workflow checks Oct 1, 2026
@Dja-m

Copy link
Copy Markdown

execute

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.

[platform-assessment 2026-10] gh-aw Drift Sentinel findings

3 participants