pages.dev domain then an employee should be able to look up the errors for youpages.dev
C
just-portal.pages.dev
A
H
C
W
WCWWCWHWHHHW
WHH
CW
ZH
GGGGGG
E
idurlalias and environment as output variables which you can pipe into whatever logic you need in the next actionEEEAll these branch URLs, they're associated with the same project, yes?Yes, you can setup preview and production builds for each project. Within preview builds there can be many branches, though as far as env vars and bindings for functions goes there can only be the production set and the preview set.
Then use push and pull_request triggers in the github actions to deploy to both of these projects from the same trigger (built with the different env vars)Yep this will work fine, just invoke
pages-action twice with different outputs and project namesIf I "invent" a branch name for the pull requests and treat it like a branch name, I can get some friendly deploy preview URLs under the pages.dev domainYep, you can do that. Something like
pr-1234 as branch or similar value.and I would want to handle the closed and merged pull request triggers to remove those same "invented" branches.Yeah you can do that with the API. List them (https://developers.cloudflare.com/api/operations/pages-deployment-get-deployments) and then delete them (https://developers.cloudflare.com/api/operations/pages-deployment-delete-deployment)
WWjust-portal.pages.devaliasenvironmentpages-actionpr-1234