Closed seabeya closed 10 months ago
Is "Create using direct upload" the way to go to create a project when you do custom deployments using GitHub Actions?
Yes it is, the GitHub Action does a Direct Upload - https://developers.cloudflare.com/pages/how-to/use-direct-upload-with-continuous-integration
(related issues: https://github.com/cloudflare/pages-action/issues/51)
This error occurs when attempting to publish to a non-existing Cloudflare Pages project using GitHub Actions.
There are two options/ways to create a project as I see:
Option/Way 1:
Create by importing an existing Git repository
.Connect the GitHub repo
->Name the new project
->Click deploy to finish the setup
.Then, pause automatic deployments (from Build & deployment settings) because I'm going to use GitHub Actions for that. I don't need Cloudflare to do this for me.
Now, every time I push, there will be two deployments: one created by Cloudflare (skipped), and one created by my GitHub workflow.
Option/Way 2:
Create using direct upload
.Name the new project
->Click "Create project"
(No need to finish the process by clicking deploy. All we need was creating a project).The question is:
Is "Create using direct upload" the way to go to create a project when you do custom deployments using GitHub Actions?