Skip to content

feature request: compile time validation for front matter trigger conditions #28957

@jamesadevine

Description

@jamesadevine

I configured a workflow to enable PR review on copilot PRs through a slash command trigger:

---
on:
  slash_command:
    name: rust-review
    events: [pull_request, pull_request_comment]
  bots:
    - "copilot[bot]"
description: On-demand Rust code review triggered by /rust-review command on PRs
permissions:
  contents: read
  pull-requests: read
  issues: read
tools:
  github:
    toolsets: [default]
network:
  allowed: [defaults, rust]
safe-outputs:
  add-comment:
    max: 3
---

However, the slash command did not work on initial PR creation by copilot. I believe this is because when the PR was created, the slash command action was triggered due to bots being specified, and then when I actually did invoke the slash command in the PR thread, my request was ignore as the action was already in progress. Of course, the bot trigger is refused for copilot[bot].

With the bot trigger removed, this conflict no longer exists.

What I would like to see

Compile time warnings of such conflicts (if possible).

Metadata

Metadata

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions