chore(bixarena): only accept deployment from tmp branches protected by rulesets #1481
Conversation
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
zaro0508
approved these changes
Oct 10, 2025
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.
Description
Further restrict the branches that can trigger a BixArena deployment during the IaC development phase to only those protected by GitHub rulesets. Currently, these rulesets allow only Sage monorepo administrators to create or modify branches that match the newly proposed branch naming pattern.
This PR addresses this comment.
Once the IaC and GitHub workflows are complete, and we can ensure that only authorized events and users can trigger deployments, a new PR will be opened to add main back to the list of branches allowed to trigger a deployment.
Cc: @zaro0508