Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
@Lensflare I don't actually know if this is the correct answer. I just upvoted it because the shortness of it seemed snarky.
-
galena71752y@vintprox We have a main project that gets adjusted to a customer's needs. So every customer has their own repo. Pushing changes from main to every customer requires this many remotes. And 30 is just a fraction of what is out there.
-
@galena wouldn’t it make more sense if those customers used that main project as a library and just pulled the changes regularly? Or as a submodule.
30 remotes sounds insane. -
galena71752y@Lensflare Thing is, its a bare metal project. We also make all the changes to it. Customer never sees a line of code. Libraries and submodules are out of question. The part of the dev team doing the configuration never sees any of this. They just have their project they work on for some time and are done with it. I mainly cherry pick all important changes to older projects. Thats what the remotes are for.
Why the fuck is my git slower than a lobotomized snail when running a fetch operation on like 30 remotes?!?!
rant