Concur. Composability, separation of concerns, do one thing and one thing well, etc. are all philosophies as old as time in this industry. Any programmer worth

Concur. Composability, separation of concerns, do one thing and one thing well, etc. are all philosophies as old as time in this industry. Any programmer worth their salt would understand the value they provide. Source code hosting has nothing to do with building your software and it's a bad idea to mix them up. This situation is actually a bit more insidious. All these CI/CD features are just a thinly veiled attempt at locking users into the platform. There's not big money to be made selling git hosting, but if you control how the software is built, then you have made yourself a hard dependency. If you look at the starter workflows they provide, they encourage bad practices where your application build is defined in their DSL. Experienced programmers might steer away from such usage, but many novice won't. If you have enough novice adoption, it becomes the norm. So many projects these days cannot even be built locally without a CI service dependency, where instead 99% of the time, all you needed was a simple makefile.