Closed sync-by-unito[bot] closed 6 months ago
➤ James Chien commented:
Sam Do you have any thought about this topic?
➤ Sam commented:
James Chien, Use separate private repo seems more simpler to me. Without further research I can see that we just need to
For Use the original capture-lite repo and add scripts and configs ...
➤ James Chien commented:
It seems forked repo cannot go private. I'll try to clone it and add capture-lite as upstream instead.
Some ref: Create a private fork of a public repository (github.com) ( https://gist.github.com/0xjac/85097472043b697ab57ba1b1c7530274 )
➤ James Chien commented:
https://github.com/numbersprotocol/capture-cam-lollipop ( https://github.com/numbersprotocol/capture-cam-lollipop )
Sam Is Capture Cam iOS currently release to Testflight manually? If so I think we can ignore the github action in Capture Cam Lollipop for now.
➤ Sam commented:
James Chien, yes Capture Cam iOS currently release to Testflight manually because of [fix] ios GitHub CI ( https://app.asana.com/0/0/1205880910641438 ).
To white-label the Capture Cam, e.g. create different build flavors with different features or assets based on the same core codebase, there may be two approaches.
Use the original capture-lite repo and add scripts and configs to allow invoking builds for different flavors
Pros:
Cons:
Use separate private repo
Pros:
Cons:
Consider the current case, I think working in a separated private repo is better and we can put the Lollipop branding materials in the repo without worrying how do we handle them in open-sourced Capture Cam.
┆Issue is synchronized with this Asana task by Unito ┆Created By: James Chien