#Multiplatform project management

1 messages · Page 1 of 1 (latest)

fierce radish
#

In relation to source control, what is the recommended method for managing a single Unity project that will be deployed to multiple platforms? Each platform requires different methods that will change the codebase or the general setup and settings of the project, so a shared main branch will not be able to hold all changes for each platform. Unless it can, and I'm uninformed on the process.

Ideally, there would be a universal main branch that accepts all generic changes to assets, with a number of platform branches that automatically stay up to date with the universal main branch, but while also holding their own platform specific changes.

I've read about some users who set up separate repositories for each platform, some who have platform specific branches that run alongside the main branch, and some who keep platform specific Unity projects within their main project folder. The second solution sounds closest to what I'd like, but it will require some manual effort to keep each platform branch updated with daily changes.

Specifically, we're using Unity with Github and Github Desktop. Any advice on best practice for this would be much appreciated. 🙂

surreal path
#

What kind of things are you tweaking in a project for different platforms so differently that would make them not work in a single project?

#

Ideally, we expect people to use one project and deploy it to all platforms we support. We don't want you to have to fork your project so I'm wondering in which ways specifically that doesn't work.

cursive radish
raven cipher
#

You can use unity with github to import github package.

#

also github destop for unity

#

Follow these steps.