Skip to content

Give the v4 workflow its own file name #2990

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
nohwnd merged 1 commit into from
Aug 22, 2026
+6 −3
Merged

Give the v4 workflow its own file name #2990

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 6 additions & 3 deletions .github/workflows/ci.yml → .github/workflows/ci-v4.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,11 +5,14 @@
# releasable: green CI here means a security fix can be validated and shipped
# through the manual release process (release.ps1).
#
# The name differs from the workflow on main and on rel/5.x.x on purpose.
# The file name and the workflow name differ from main and rel/5.x.x on purpose.
# test-report.yml on main runs after every workflow named "CI" and renders its
# results, and Pester 4 can only write NUnit 2.5 XML, which dorny/test-reporter
# cannot read. The gate job below is still called "Done", same as everywhere
# else, that is the name branch protection requires.
# cannot read. A workflow is identified by its file path, and its name comes
# from the copy on the default branch, so while this file was also called
# ci.yml the rename alone did nothing and the report kept running and failing.
# The gate job below is still called "Done", same as everywhere else, that is
# the name branch protection requires.
name: CI (v4)

on:
Expand Down