Skip to content

fix(ci): rename copilot review workflow to avoid reserved name - #11159

Merged
robert-hebel-sb merged 1 commit into
mainfrom
ci/rename-copilot-review-workflow
Nov 20, 2026
Merged

robert-hebel-sb merged 1 commit into
mainfrom
ci/rename-copilot-review-workflow

Conversation

@robert-hebel-sb

Copy link
Copy Markdown
Contributor

Description

Rename .github/workflows/copilot-code-review.yml to .github/workflows/request-copilot-review.yml. File contents are unchanged.

Motivation and Context

Follow-up to #11156. copilot-code-review.yml is a name Copilot reserves: it reads the file as the setup-steps file for Copilot code review and expects a job named copilot-code-review. Our workflow (which requests a Copilot review only when the PR author is listed in .github/CODEOWNERS) used that filename with a job named request-copilot-review, so Copilot failed with:

no supported setup-steps job found in your workflow file. Please ensure you have a job named copilot-code-review or copilot-setup-steps.

The new filename matches the job name and is no longer treated as a Copilot setup file.

Note: the repository ruleset option "Automatically request Copilot code review" must stay off, otherwise Copilot reviews every PR regardless of this workflow.

How Has This Been Tested?

Not tested end to end yet. Because the workflow uses pull_request_target, it only runs from the version on main after merge. The check to do after merge is to open a PR as a codeowner and confirm Copilot is requested as a reviewer, and open one as a non-codeowner and confirm it is not.

Screenshots (if appropriate):

N/A

Checklist

My PR contains...

  • No code changes (src/ is unmodified: changes to documentation, CI, metadata, etc.)
  • Dependency changes (any modification to dependencies in package.json)
  • Bug fixes (non-breaking change which fixes an issue)
  • Improvements (misc. changes to existing features)
  • Features (non-breaking change which adds functionality)

My changes...

  • are breaking changes to a public API (config options, System API, major UI change, etc).
  • are breaking changes to a private API (Redux, component props, utility functions, etc.).
  • are breaking changes to a developer API (npm script behavior changes, new dev system dependencies, etc).
  • are not breaking changes.

Documentation

  • My changes do not require a change to the project documentation.
  • My changes require a change to the project documentation.
  • If yes to above: I have updated the documentation accordingly.

Automated tests

  • My changes can not or do not need to be tested.
  • My changes can and should be tested by unit and/or integration tests.
  • If yes to above: I have added tests to cover my changes.
  • If yes to above: I have taken care to cover edge cases in my tests.
  • All new and existing tests passed.

🤖 Generated with Claude Code

.github/workflows/copilot-code-review.yml is a reserved name that Copilot
reads as the setup-steps file for code review and expects a job named
copilot-code-review. Our trigger workflow used that filename with a job
named request-copilot-review, so Copilot failed with "no supported
setup-steps job found in your workflow file".

Rename the file to request-copilot-review.yml. Contents are unchanged.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@github-actions
github-actions Bot requested a balanced review from Copilot November 20, 2026 10:01

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Copilot wasn't able to review any files in this pull request. Check if the Files changed in this pull request are included in default exclusions.

@robert-hebel-sb
robert-hebel-sb merged commit 16fb3db into main Nov 20, 2026
10 checks passed
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