GitHub Community
Are atomic multi-repositories pushes possible? #120704
-
Select Topic AreaQuestion BodyWith multi-repo / poly-repo projects, sometimes it's important for repositories to be updated in lockstep (especially when the project is badly managed or only multi-repo because of hype). I know that git supports atomically updating multiple refs since 2.4, and github supports that as well, however is there a good way to perform atomic multi-repo updates? I don't believe github provides repo locks, so an application-side 2PL or similar does not seem possible, and in my experience Github's cross-repository anything are rather limited. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
This comment was marked as spam.
This comment was marked as spam.
-
|
Thanks, that's about what I'd figured but I appreciate the exhaustivity. Sadly the setup is out of my hands (and furthermore generally has justifiable business reasoning behind it or at least some of it). We do implement (2), (6), and (7) and the question was in part in that context: they're not foolproof / error-free, and as github is not always reliable these days and it can be difficult to envision all possible failure cases (or recover from them) (2) can have pretty difficult edge cases, and I wanted to know if there were ways to improve that I had missed. Sadly it seems that's not the case. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @david-wei-01001 , We’ve clarified our stance on using generative AI tools like ChatGPT within our Community via this announcement. Please review the guidelines to ensure your post meets them as failure to adhere to those rules can result in action taken by our moderator team. You can read our updated Code of Conduct and the announcement for more details. Thank you for helping us maintain an authentic and beneficial space for everyone. |
Beta Was this translation helpful? Give feedback.
As of my last update, there isn't a built-in mechanism in Git or GitHub to perform atomic transactions across multiple repositories. Git’s atomic operations generally apply to actions within a single repository, such as updating multiple refs in one push to that repository.
When dealing with multiple repositories (multi-repo or poly-repo), atomicity becomes more complex because each repository has its own commit history and ref namespace. Here are some considerations and potential workarounds:
Submodules/Subtrees: If you want to keep repositories in sync, you could consider using Git submodules or subtrees, which allow one repository to include content from another. However, this doesn'…