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
Currently, sync steps wait on their individual sync branches before pushing new commits. We could create a prerequisite step that requires all sync branches to be synced before pushing any of them.
Alternatively we could make it so that syncing "succeeds" automatically if the sync point is behind main - that is, we could make it possibly to retry runs without resetting all the sync branches. This would reduce the complexity of resolving the issue significantly by allowing one branch to catch up just by re-running jobs on Cloud Build rather than taking manual steps. this is covered by #12360 and is a separate consideration regardless of whether we force downstream builder to wait.
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Currently, sync steps wait on their individual sync branches before pushing new commits. We could create a prerequisite step that requires all sync branches to be synced before pushing any of them.
Doing so would remove the possibility of Divergence by more than one commit scenario. This is the most complicated scenario to resolve.
The text was updated successfully, but these errors were encountered: