I have no experience with source controlling Unity files and Projects with Github (I have knowledge of Github itself and how to use it)).

Cloud build / Collaborate apparently does not support branching (always builds on commit but sometimes those are used for 'transferring' progress to another machine), Cloud build is quite difficult to customize to our needs (would have to somehow upload the files after build to the blob storage (supposedly via FTP or something similar).

My Ideas so far where using Unity Cloud Build (as we already have Unity plus and Teams advanced) or using Github Actions and source controlling it via a Git repository.

They have the 'work' of uploading the game via the second webappīecause of these concerns I wanted to automate this process.

The developers all build the Games on their dev Machines which 'locks' the PC from any other use / further development.

This upload happens through a separate Page I set up for the various Developers we have in the Team.

I am currently showing those Games via WebGL on a Website that requests the data files (wasm, data etc.) from an Azure Blob Storage where I upload the files to. More or less those are multiple 'minigames' that all have the same foundation. Im a currently working on mutliple Unity projects that share quite a lot of prefabs, scripts etc.

Unity cloud build manifest example