How to manage repositories in a multi-tenant white-label project?

[giorgionocera]

We need to get some references about managing a multi-tenant white-label project like our picowallet. This is necessary since we need to understand how we'll perform upstream fetches for the specific repositories when an update affects all of them and it is done on the main picowallet repo.

I ask we all paste here all the references we can find, to be able to produce our "standard" guideline about this functioning.

Thank you! 😄

[DavideSegullo]

I found some references:

• https://nqaze.medium.com/managing-white-label-solutions-8ed8ce9d7fa8

[giorgionocera]

Thank you @DavideSegullo for this reference. I looked at that link and I don't like so much those approaches.
In particular, I don't know if the creation of new branches on the same repository could fit the needs of our implementation. I'm scared about the mess we can generate on the repo thinking about bug fixes for each customer, specific custom features, and so on...
What do you think about forking the repo? As I said at the beginning?
I'll also look for other references (if you have time, please continue looking 😄)

[DavideSegullo]

Ye, fork is much better, I'll give a look for some references