Onboard new CI checks (alpha tier) - #549
Conversation
adecler
left a comment
There was a problem hiding this comment.
This Repo is part of the installer (to be checked) so it should be in the beta tier.
|
Test_Toolkit isn't in the installer: Agree it should probably have beta checks but I feel like in the past it has failed checks (e.g. compliance) because it is set up differently to traditional toolkits (and has a different function). |
|
Historical PRs + existing branch protection settings all characterise Test_Toolkit as an alpha marked repository i.e., only |
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
|
@BHoMBot check required |
|
@sakanni to confirm, the following actions are now queued:
There are 1 requests in the queue ahead of you. |
|
@BHoMBot check copyright-compliance |
|
@sakanni to confirm, the following actions are now queued:
There are 7 requests in the queue ahead of you. |
|
This repository is not part of the beta package and does not require a versioning check to be performed. |
|
This repository is not part of the installer package, and does not require an installer check. |
|
@BHoMBot check required |
|
@sakanni to confirm, the following actions are now queued:
|
|
This repository is not part of the beta package and does not require a versioning check to be performed. |
|
This repository is not part of the installer package, and does not require an installer check. |
adecler
left a comment
There was a problem hiding this comment.
All expected jobs added with the ci prefix
Adds the alpha-tier CI workflow as part of the new CI onboarding pilot for framework repositories.
The checks run on pull requests and are non-blocking during the evaluation period. On this PR they will pass within seconds since no code changes: the first code PR after merging exercises them fully.
Details and discussion: BuroHappoldEngineering/CI_Toolkit_Proxy#13