Repository navigation
Conversation
Every ref in the bundle points at BHoM/CI_Toolkit rather than the redirect, so this exercises the new path directly. The touched source file keeps the changed-file gate from skipping the checks. Not for merge.
Contributor
Author
|
Validation complete. Every ref in the bundle pointed at BHoM/CI_Toolkit and eight of nine checks passed; ci-versioning failed on the two known findings (TryGetValueFromSource, ProjectParameter), byte-identical to yesterday's runs on the Admin path. The private mock clone worked: all five mocks copied via an App token scoped to the mock repo's own org. Not for merge. |
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
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.
Validation only. Every ref in the bundle points directly at
BHoM/CI_Toolkit, not at the redirect, so this tests the new path rather than the fallback.What is under test: private dependency cloning still works.
ci-versioningmints a second App token scoped to the mock repository's own org rather than the caller's, and clones a private repository from a public workflow. That is the path the transfer could plausibly have broken, and the mock clone is not cache-gated, so a warm cache cannot make the run vacuous.