When utilising the UI based/provided Github connection, it seems as though the Config path search is not scoped to the ‘Branch to deploy’ and instead is scoped to the ‘main’ branch only.
Meaning when we attempt to deploy an app from the ‘staging’ ‘Branch to deploy’ that has no fly-staging.toml in the ‘main’ branch, but does in ‘staging’ we get a ‘Config file not found…’ error.
Hey @hdroguetta, from my understanding we expect the fly-staging.toml to exist in you main git branch, we have lots of internal examples of that pattern being used. Is there a particular reason why you’re not including the staging TOML in your main git branch?
This would prevent you from pushing to staging manually from the cli with flyctl from your main branch which in theory is something you may want to do.
