Skip to content

Commit f033e23

Browse files
henrymercerCopilot
andcommitted
Clarify why the file baseline check uses a custom configuration
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
1 parent 0171a2b commit f033e23

2 files changed

Lines changed: 2 additions & 2 deletions

File tree

‎.github/workflows/__export-file-baseline-information.yml‎

Lines changed: 1 addition & 1 deletion
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

‎pr-checks/checks/export-file-baseline-information.yml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ steps:
1919
tools: ${{ steps.prepare-test.outputs.tools-url }}
2020
# To balance speed and coverage, analyze only JavaScript but use the combined bundle so
2121
# baseline information is reported for every language in the multi-language repository. A
22-
# no-op custom configuration selects that conservative path for custom configurations.
22+
# custom configuration prevents per-language bundles from being used.
2323
config: |
2424
paths-ignore: []
2525
- name: Build code

0 commit comments

Comments
 (0)