Push policy based stack locking
We're excited to announce yet another VCS improvement: Stack locking using a Push policy. This new feature is particularly useful in workflows heavily reliant on pull requests, as it adds additional control over their merge order.
This push policy update introduces optional
lock and unlock rules, which use user-defined keys for locking and unlocking stacks based on certain criteria. A failed lock attempt due to an existing different key prevents new run creation and sends a failure message to the VCS, helping to ensure a better controlled change order in workflows dependent on pull requests.Feel free to reach out if you have any questions or need assistance in setting it up!