You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 21, 2024. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
nader-eloshaiker
changed the title
Trank based development and differentiating preview vs production env
Trunk based development and differentiating preview vs production env
Jan 15, 2024
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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, 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 the
branch
property incloudflare/pages-action
and it seems to work well. I use the valuebranch: stagging
for feature merges andbranch: main
for production.However, what I have noticed in GitHub and in
google-github-actions/release-please-action
source 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.The text was updated successfully, but these errors were encountered: