ci: prefix CI check names to avoid BHoMBot collision - #87
Conversation
|
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 233 requests in the queue ahead of you. |
1 similar comment
|
@BHoMBot check copyright-compliance |
1 similar comment
|
@BHoMBot check copyright-compliance |
|
@BHoMBot check |
6 similar comments
|
@BHoMBot check |
|
@BHoMBot check |
|
@BHoMBot check |
|
@BHoMBot check |
|
@BHoMBot check |
|
@BHoMBot check |
|
@BHoMBot check ready-to-merge |
|
@sakanni to confirm, the following actions are now queued:
There are 2 requests in the queue ahead of you. |
|
@sakanni to confirm, the following actions are now queued:
There are 2 requests in the queue ahead of you. |
adecler
left a comment
There was a problem hiding this comment.
ci prefix correctly added to all jobs
|
@sakanni to confirm, the following actions are now queued:
There are 43 requests in the queue ahead of you. |
Renames the CI job keys to a ci- prefix so their status-check contexts no longer collide with BHoMBot. When both post the same context name, only the first wins the slot and BHoMBot is suppressed, leaving the BHoMBot-pinned required checks unsatisfied and blocking merges. The ci- prefix lets BHoMBot resume its bare-named checks with no branch-protection change. Source change: BuroHappoldEngineeringAdmin/CI_Toolkit#124.