← Back to context Comment by thirtyseven 17 hours ago Roku uses Gitlab internally so could just be a standardization thing. 4 comments thirtyseven Reply midnightclubbed 16 hours ago Moving changes back and forth between gitlab and github is a pain. Could indeed be as simple as standardization and reducing development pains. otterley 16 hours ago What makes it more complicated than doing a Git push against two remotes? Assuming that one of those is used for collaboration and the other is just a mirror. darkstar999 16 hours ago The CICD pipeline is not directly compatible, for one. 1 reply →
midnightclubbed 16 hours ago Moving changes back and forth between gitlab and github is a pain. Could indeed be as simple as standardization and reducing development pains. otterley 16 hours ago What makes it more complicated than doing a Git push against two remotes? Assuming that one of those is used for collaboration and the other is just a mirror. darkstar999 16 hours ago The CICD pipeline is not directly compatible, for one. 1 reply →
otterley 16 hours ago What makes it more complicated than doing a Git push against two remotes? Assuming that one of those is used for collaboration and the other is just a mirror. darkstar999 16 hours ago The CICD pipeline is not directly compatible, for one. 1 reply →
Moving changes back and forth between gitlab and github is a pain. Could indeed be as simple as standardization and reducing development pains.
What makes it more complicated than doing a Git push against two remotes? Assuming that one of those is used for collaboration and the other is just a mirror.
The CICD pipeline is not directly compatible, for one.
1 reply →