cloudflare / pages-action

MIT License
440 stars 91 forks source link

Project not found. The specified project name does not match any of your existing projects. #115

Closed seabeya closed 6 months ago

seabeya commented 6 months ago

(related issues: https://github.com/cloudflare/pages-action/issues/51)

API returned: {
  "result": null,
  "success": false,
  "errors": [
    {
      "code": 8000007,
      "message": "Project not found. The specified project name does not match any of your existing projects."
    }
  ],
  "messages": []
}

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.

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.

image

Option/Way 2: Create using direct upload.

image


The question is:

Is "Create using direct upload" the way to go to create a project when you do custom deployments using GitHub Actions?

WalshyDev commented 6 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