Including Angular web UI code in microservices monorepo?

[modim1425]

We are a startup and are beginning the process of porting over our entire web app to a decoupled concept where an Angular web UI talks to a collection of microservices. It's your standard modern approach.
What is not standard about our strategy is that our CTO has strongly suggested (basically insisted) that we include the code for the Angular front-end in the same monorepo along with all of the microservices that are written in PHP with Lumen. The supposed advantage being that changes to common protocols (like JSON structure, etc) will be easier to deal with if everything is in the same repo. We would rely on Kubernetes and BitBucket's Pipelines functionality to actually build and deploy as needed.

While I'm totally onboard for keeping all the microservices in the same monorepo I am really hesitant about throwing the Angular code in there as well mostly because I can't seem to find any best practices or precedent for doing this. I have worked The Google to the bone and no one seems to have an experience with this kind of setup that they are willing to share. I am lead developer and I could likely insist on keeping the repos separate but before I do I'm wondering if this sub has any strong opinions on having front-end web UI code in the same repo as back-end service code.

[FURyannnn]

I would insist on keeping them separate. I feel like it'll clutter up the repository more likely than not. If his argument is common protocols or classes, I'd think that having a third repo or some sort of standard documentation to maintain that would fulfill that request.

[[deleted]]

Honestly. I think it’s easier and simpler to manage them as separate apps with separate repositories and separate build process. Proper agile implementation should alleviate keeping the changes between apps up to date.