validate: AssemblyInfo.cs alone must not trigger versioning - #15
Open
sakanni wants to merge 1 commit into
Open
Conversation
Harness pinned to CI_Toolkit fix/ci-versioning-gate-and-scan-root. The only matched change on this branch is an added AssemblyInfo.cs, so the ':(exclude)*AssemblyInfo.cs' pathspec should leave count=0 and every step should self-skip. The workflow file itself is not in the gate patterns.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Sandbox validation subject for CI_Toolkit
fix/ci-versioning-gate-and-scan-root. Not for merge.Expected:
compute-changed-filesreportscount=0andNo relevant files changed, every step in the composite self-skips, and the job is green. That confirms the:(exclude)*AssemblyInfo.cspathspec both parses in the runner's git and actually excludes at project-Propertiesdepth.No control leg: the pattern behaviour on
developis already covered bytest-changed-file-patterns.shagainst a fixture built from real repo layouts, and a control here would cost a full 20-minute versioning run to observecount=1.Serialisation fires on this branch too and ships the same exclusion already, so it should skip for the same reason.