Often, when someone works on changes that span multiple services, they think of it as a separate Pull Request for every project. Then, when it comes to deploy day, there’s a concern: We want to make a change to X but Y also needs that change to work - how do we deploy these at the same time?
In my final year of college, I got swept up in creating Twitter bots and tools. As a result, I created several different projects in Go but the go-twitter package hadn’t been updated in over a year and was missing the majority of API functionality. At first, I submitted pull requests to the original library but received sparse answers and a never-ending list of semantic changes (despite passing the Continuous Integration tests).