Skip to content

[q] Treat github-actions[bot] as trusted team member in Contribution Check #55087

Description

@github-actions

Q Workflow Optimization Report

Issues Found

Contribution Check (.github/agents/contribution-checker.agent.md)

Changes Made

Contribution Checker subagent (.github/agents/contribution-checker.agent.md)

  • Added a new Step 0: Bot / Team Author Check ahead of the existing checklist.
  • If the PR author is github-actions[bot] (or otherwise a bot/App performing automated repo maintenance), the subagent now short-circuits: it skips the full checklist and returns an immediate 🟢/lgtm verdict with an empty comment (comment: ""), so no contributor-facing comment gets posted on the PR.
  • For all other (human) authors, the existing full evaluation flow is unchanged.

Expected Improvements

  • Automated maintenance PRs opened by github-actions[bot] (e.g. Instructions Janitor docs syncs) are now treated as trusted team member contributions: evaluated as lgtm with no patronizing "thanks for your contribution" comment posted.
  • No change to behavior for human contributors — the full checklist, verdict rules, and comment generation are untouched.

Validation

This change only touches a .md agent definition file used as a prompt (.github/agents/contribution-checker.agent.md), which has no .lock.yml compilation step. gh aw compile was not applicable; the orchestrator workflow (contribution-check.md) itself was not modified.

References


Warning

Protected Files

This was originally intended as a pull request, but the patch modifies protected files. These files may affect project dependencies, CI/CD pipelines, or agent behaviour. Please review the changes carefully before creating the pull request.

Click here to create the pull request once you have reviewed the changes

Protected files

To route changes like this to a review issue instead of blocking, configure protected-files: fallback-to-issue in your workflow configuration.

🎩 Equipped by Q · auto · 25.2 AIC · ⌖ 11.4 AIC · ⊞ 12.1K ·
Comment /q to run again

  • expires on Aug 25, 2026, 6:03 AM UTC-08:00

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions