I have recently switched my repo to trunk based where by I only have a main branch and features/fixes/chores go straight into it. Further, using google-github-actions/release-please-action, I use PR's to perform the releasing process. So stagging/preview and production deployments are done from the main branch.
The my workflows are able to differentiate when to deploy to preview and production using the branch property in cloudflare/pages-action and it seems to work well. I use the value branch: stagging for feature merges and branch: main for production.
However, what I have noticed in GitHub and in google-github-actions/release-please-actionsource code, is that the GitHub environment will always be production and not preview due to the fact that they both work off main despite the value of branch passed to the action.
I have recently switched my repo to trunk based where by I only have a
mainbranch and features/fixes/chores go straight into it. Further, usinggoogle-github-actions/release-please-action, I use PR's to perform the releasing process. So stagging/preview and production deployments are done from the main branch. The my workflows are able to differentiate when to deploy to preview and production using thebranchproperty incloudflare/pages-actionand it seems to work well. I use the valuebranch: staggingfor feature merges andbranch: mainfor production. However, what I have noticed in GitHub and ingoogle-github-actions/release-please-actionsource code, is that the GitHub environment will always be production and not preview due to the fact that they both work off main despite the value of branch passed to the action.