Branch referece in client for each environment
We are trying to adopt the 'branching approach'.
Till now we have different projects representing different environments (dev, stg, prod). In our client we have different env variables to target those projects depending on the git branch we trying to build.
So far so good.
Now, If we want to keep everything in one project but target different branches depending on the environment.... how do I have to initialize the SDK in my clients? We mainly use Flutter.
This is very confusing and I dont know how to adapt our CI-CD workflow to the new branching approach.
1 Reply
In case I havent explained myself very well...
This is where I tell my client app which Supabase project needs to target; I want to be able to reference a branch there.. I guess?
Well, I am AInvestigating and it seems that the Supabase-Github integrations manages to create those variables and expose them in the PR so other CI-CD systems like CodeMagic can use those variables.
It also seems that Github is smart enough for ordering the steps so it doesnt trigger the CodeMagic (or other provider) pipeline till those variables are set by the Supabase's webhook.
I havent setup this yet, so it can be completely false.
It would be awesome to have documentation and a good explanation (video maybe) in this regard since this branching feature is tightly coupled with the CI-CD systems we have to put in place.
Thus, I am not going to mark this as resolved yet.
Thx.