ci: point the CI workflow at BHoM/CI_Toolkit - #551
Merged
Conversation
peterjamesnugent
approved these changes
Aug 17, 2026
peterjamesnugent
left a comment
peterjamesnugent
left a comment
Member
There was a problem hiding this comment.
Happy with changes just repointing the path to BHoM/CI_Toolkit as evidenced by the checks passing,
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
2 participants
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.
CI_Toolkit moved from BuroHappoldEngineeringAdmin to BHoM. The old path redirects, so this removes a dependency on the redirect rather than fixing a break.
Also picks up a pattern correction made since this file was copied: project compliance matches
AssemblyInfo.csat any depth instead of only at the repo root. It does not change which files are selected in this repo today.Worth recording while this file is being touched: this repository carries no
maturitycustom property. The alpha tier here is a pragmatic choice so the repo gets the checks, not a classification. Nobody should later readci-alpha.ymlas evidence that alpha was decided for it.Still non-blocking. Tracked in CI_Toolkit_Proxy#13.