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,
I'm able to create 2 stacks for the same repo & branch.
If Merge-Queue is enabled on both, they can interfere with each other.
Suggestion:
Merge-Queue can be enabled only once for a given set of Repo & Branch, regardless of the stack environment.
moduleShipitclassStack < RecordmoduleNoDeployedCommit...
validates:merge_queue_enabled,uniqueness: {scope: %i(repositorybranch),message: 'cannot be used more than once with this repository and branch. Check (archived) stacks.'}...
The text was updated successfully, but these errors were encountered:
For backward compatibility, I can add a flag that indicates if this validation should be enforced.
The flag can be added to the repository module: "Single CI per branch".
Currently,
I'm able to create 2 stacks for the same repo & branch.
If Merge-Queue is enabled on both, they can interfere with each other.
Suggestion:
Merge-Queue can be enabled only once for a given set of Repo & Branch, regardless of the stack environment.
The text was updated successfully, but these errors were encountered: