[CI] A TestFlight build is created for each commit 🤯

[g123k]

Hi everyone,

We currently have a GitHub Action that sends each commit from the dev branch to TestFlight.
I'm not sure it is that relevant to send so many builds (and consume so much power for nothing).

Shouldn't we use a manual trigger instead?

[M123-dev]

Yes, we wanted it like this for testing. Now that we have waldo it is probably not needed anymore

If we decide against it its just removing

.github/workflows/internal-release.yml

it calls the release for the play and app store

[g123k]

Is-it OK for you @teolemon that we disable this?

[teolemon]

• I don't understand why Android internal would still be on every commit and Apple TestFlight wouldn't.
• Anyway, if we end up disabling this, We need a button to trigger the action for a TestFlight release

[g123k]

• I don't understand why Android internal would still be on every commit and Apple TestFlight wouldn't.

The idea is to remove both.
This is an abnormal behavior to send every commit on dev to the stores.

• Anyway, if we end up disabling this, We need a button to trigger the action for a TestFlight release

It would just consist of launching manually the same action

[M123-dev]

A month ago I would have said that we could just use release please for that

but now F-Droid is linked to it so every new release means a public release on F-Droid no way to publish them on a later date

[g123k]

Mmm, seems OK now, isn't it?

[teolemon]

Yes we can close