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
Is your feature request related to a problem? Please describe.
We using a huge monorepo with multi argocd application.
Each application has a different git write back branch.
There are case that 1 image change create more than 300 application update. Each update need to wait for each other because we have a mutex for same git repo url.
Describe the solution you'd like
From #177 , we have a mutex when pushing to git. But the key is base on git url. I think we can change mutex key to something like gitUrl:targetBranch
Additional context
We don't directly push to master branch because of our company audit policy, which need approve from CODEOWNER to push any change into production.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
We using a huge monorepo with multi argocd application.
Each application has a different git write back branch.
There are case that 1 image change create more than 300 application update. Each update need to wait for each other because we have a mutex for same git repo url.
Describe the solution you'd like
From #177 , we have a mutex when pushing to git. But the key is base on git url. I think we can change mutex key to something like
gitUrl:targetBranch
Additional context
We don't directly push to master branch because of our company audit policy, which need approve from CODEOWNER to push any change into production.
The text was updated successfully, but these errors were encountered: