You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm looking to see how folks are setting branch protection rules with stack-pr. Normally, we only have branch rules on master, meaning that you need a PR with a certain number of approvers to commit to this branch.
master <- A <- B <- C.
Stack-pr will create different branches for each of these. Landing A requires an approval. However, landing B & C technically don't.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hey all,
I'm looking to see how folks are setting branch protection rules with
stack-pr
. Normally, we only have branch rules onmaster
, meaning that you need a PR with a certain number of approvers to commit to this branch.master <- A <- B <- C
.Stack-pr will create different branches for each of these. Landing A requires an approval. However, landing B & C technically don't.
Beta Was this translation helpful? Give feedback.
All reactions