Skip to content

fix: disable schedule/event trigger UI (pending GitHub App Copilot entitlements) - #937

Closed
sabbour wants to merge 2 commits into
devfrom
fix/disable-automation-triggers
Closed

fix: disable schedule/event trigger UI (pending GitHub App Copilot entitlements)#937
sabbour wants to merge 2 commits into
devfrom
fix/disable-automation-triggers

Conversation

@sabbour

@sabbour sabbour commented Aug 26, 2026

Copy link
Copy Markdown
Owner

Summary

Scheduled and event-based (webhook) triggers cannot safely run without a live user's Copilot identity. GitHub Apps don't yet have Copilot entitlements, so automation triggers have no valid identity source.

Changes:

  • WorkflowsPage.tsx: Add schedule/Edit schedule and event trigger buttons disabled, replaced with a tooltip explaining this is a future enhancement and linking to github/copilot-sdk#551
  • WorkflowScheduleTriggerService.cs: Backend guard (AutomationTriggersEnabled = false) makes ExecuteAsync return early, preventing the hosted background loop from ever firing stored schedules
  • WorkflowsPage.test.tsx: updated tests that previously drove the schedule/event dialogs via the (now disabled) buttons to instead assert the buttons render disabled with the coming-soon tooltip; badge-rendering coverage is unchanged

Re-enabling: Flip AUTOMATION_TRIGGERS_ENABLED in WorkflowsPage.tsx and AutomationTriggersEnabled in WorkflowScheduleTriggerService.cs to rue once GitHub ships Copilot entitlements for GitHub Apps.

Closes: N/A (tracks github/copilot-sdk#551)


Co-authored-by: Copilot 223556219+Copilot@users.noreply.github.com

…pp Copilot entitlements)

Adds AUTOMATION_TRIGGERS_ENABLED = false constant in WorkflowsPage.tsx.
Schedule and event trigger buttons are replaced with disabled variants
showing a tooltip linking to github/copilot-sdk#551.

Backend WorkflowScheduleTriggerService returns early in ExecuteAsync when
AutomationTriggersEnabled is false, preventing stored schedules from firing
without a Copilot identity.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 006365ea-32d3-4bd1-9abc-1a373fc4b208
@github-actions

Copy link
Copy Markdown
Contributor

📝 Docs sync reminder

This PR changes code in doc-relevant paths but does not touch docs/**.
If this change adds or alters a feature, API endpoint, MCP tool, blueprint, or workflow,
please update the docs in the same PR (the definition of done includes docs).

Changed source files
apps/Agentweaver.Api/Workflows/WorkflowScheduleTriggerService.cs

How to update fast

  • Invoke the agentweaver-docs-sync skill (.copilot/skills/agentweaver-docs-sync/SKILL.md) for the playbook.
  • Regenerate auto-derived reference: node scripts/gen-docs.mjs then commit.
  • Build to verify: cd docs && npm ci && npm run build.

This is a non-blocking reminder — it will not prevent merge. See .github/DOCS_SYNC.md.

… triggers

Beat 3.1: 'Schedule recurring dependency sweeps' -> 'Run dependency sweep on demand'
Beat 3.2: 'Trigger bug triage from GitHub' (webhook config) -> 'Manually trigger bug triage'

Scheduled and event-based triggers disabled in UI pending GitHub App Copilot
entitlements. Demo now shows on-demand manual runs via the 'Run now' button on
the Workflows page, using the real 'Queued a run for "..."' confirmation toast.

Removed the now-unused AGENTWEAVER_DEMO_GITHUB_TRIAGE_ISSUE_URL and
AGENTWEAVER_DEMO_GITHUB_TRIAGE_RUN_URL preflight externalArtifacts entries
since beat 3.2 no longer configures a webhook/event trigger.

NOTE: Narration WAVs and narration/blueprint-narration.md for beats 3.1 and 3.2
need re-recording/rewriting to match the new on-demand narrative.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 006365ea-32d3-4bd1-9abc-1a373fc4b208
@sabbour
sabbour marked this pull request as draft August 27, 2026 18:20
@sabbour

sabbour commented Aug 28, 2026

Copy link
Copy Markdown
Owner Author

Closing as superseded by Fleet automation activation in #948. This temporary automation-disable design must not merge.

@sabbour sabbour closed this Aug 28, 2026
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.

2 participants