PRs fail to create due to Error: For same-org, cross-repo pulls, 'head_repo' is required: {"resource":"PullRequest","field":"head","code":"invalid"} #1459

davereid-pfg · 2023-01-04T22:57:50Z

Subject of the issue

I have a workflow that is pushing the branch but failing to create the pull request due to a new error, when the action has worked before:

      - name: Generate token using the Github App
        uses: tibdex/github-app-token@v1
        if: ${{ env.UPDATER_APP_ID && env.UPDATER_PRIVATE_KEY }}
        id: app-token
        with:
          app_id: ${{ env.UPDATER_APP_ID }}
          private_key: ${{ env.UPDATER_PRIVATE_KEY }}
      - name: Create pull request containing any changed files
        id: create-pull-request
        uses: peter-evans/create-pull-request@v3
        with:
          branch: scheduled-updater-changes
          base: ${{ github.base_ref || github.ref_name }}
          delete-branch: true
          token: ${{ steps.app-token.outputs.token || secrets.GITHUB_TOKEN }}
          title: Automatic dependency updates
          body: Rest of the body truncated, not important.

Steps to reproduce

Logs where the workflow fails:

Run peter-evans/create-pull-request@v3
  with:
    branch: scheduled-updater-changes
    base: main
    delete-branch: true
    token: ***
    title: Automatic dependency updates
    body: Rest of the body truncated, not important.
    add-paths: -A
  
    commit-message: [create-pull-request] automated change
    committer: GitHub <[email protected]>
    author: Reid-Dave_pfghub <[email protected]>
    signoff: false
    draft: false
...
Pushing pull request branch to 'origin/scheduled-updater-changes'
  /usr/bin/git push --force-with-lease origin HEAD:refs/heads/scheduled-updater-changes
  remote: 
  remote: Create a pull request for 'scheduled-updater-changes' on GitHub by visiting:        
  remote:      https://github.com/***/private-repo/pull/new/scheduled-updater-changes        
  remote: 
  To https://github.com/***/private-repo
   * [new branch]      HEAD -> scheduled-updater-changes
Create or update the pull request
  Attempting creation of pull request
  Error: For same-org, cross-repo pulls, 'head_repo' is required: {"resource":"PullRequest","field":"head","code":"invalid"}

I cannot link to the actual logs since it is a private repository.

The same exact workflow from Dec 22 succeeded:

Run peter-evans/create-pull-request@v3
  with:
    branch: scheduled-updater-changes
    base: main
    delete-branch: true
    token: ***
    title: Automatic dependency updates
    body: Rest of the body truncated, not important.
    add-paths: -A
  
    commit-message: [create-pull-request] automated change
    committer: GitHub <[email protected]>
    author: Reid-Dave_pfghub <[email protected]>
    signoff: false
    draft: false
...
Pushing pull request branch to 'origin/scheduled-updater-changes'
  /usr/bin/git push --force-with-lease origin HEAD:refs/heads/scheduled-updater-changes
  remote: 
  remote: Create a pull request for 'scheduled-updater-changes' on GitHub by visiting:        
  remote:      https://github.com/***/private-repo/pull/new/scheduled-updater-changes        
  remote: 
  To https://github.com/***/private-repo
   * [new branch]      HEAD -> scheduled-updater-changes
Create or update the pull request
  Attempting creation of pull request
  Created pull request #12 (***:scheduled-updater-changes => main)

I'm also not able to replicate this consistently. The same exact workflow works fine in another private repository, it seems to be this specific repository causing the issue.

The text was updated successfully, but these errors were encountered:

yktakaha4 · 2023-01-05T00:39:37Z

I just encountered the same error.
It occurred in the organization's private repository, so it could be a factor.

chachasikes · 2023-01-05T01:21:25Z

Following

Similar issue - started 6-7 hours ago from the time of writing this message.
We are still getting this error.
This is the error we got in the build output:

DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.

chachasikes · 2023-01-05T01:22:12Z

Didn't see any issues with GitHub Actions for today
https://www.githubstatus.com/

peter-evans · 2023-01-05T01:25:52Z

Thanks for the report. I'm looking into this.

There haven't been any changes to the action that I think could have caused this, so it's likely to be a change with GitHub's API.

@chachasikes The deprecation warning is unrelated. See #1336

jbum · 2023-01-05T02:02:21Z

Can confirm it's happening with v4 (I'm working with @chachasikes )

quantumfusion · 2023-01-05T02:03:14Z

I can confirm the problem is still there with v4. Also running in a private repo, I have consistently had the 'head_repo' is required error.
Relevant snippets from the run on the private repo:
From setup, confirms using latest published version of the action

Wed, 04 Jan 2023 23:58:40 GMT Download action repository 'peter-evans/create-pull-request@v4' (SHA:2b011faafdcbc9ceb11414d64d0573f37c774b04)

And the same error as mentioned in OP:

Thu, 05 Jan 2023 00:12:39 GMT
Create or update the pull request
Thu, 05 Jan 2023 00:12:39 GMT   Attempting creation of pull request
Thu, 05 Jan 2023 00:12:40 GMT   Error: For same-org, cross-repo pulls, 'head_repo' is required: {"resource":"PullRequest","field":"head","code":"invalid"}

The theory around it being an API seems plausible, our last working run was at Wed, 04 Jan 2023 21:30:52 GMT.

peter-evans · 2023-01-05T02:14:04Z

I've created a GitHub support ticket because I'm fairly sure this is a change to the API they have made. I don't know if it's intentional, but if it is the documentation is incorrect and there was no warning.

peter-evans · 2023-01-05T02:38:18Z

I'm unable to reproduce this issue. Please could you explain a bit more about your scenario.

Are you creating a pull request remotely? (In a repo other than where the workflow is running)
Is the repo where the workflow runs private?
Is the remote repo private?
What type of token are you using? What scopes?
Are the repos in an org or user account?

chachasikes · 2023-01-05T02:59:43Z

@jbum & I reporting that our repo is public

jbum · 2023-01-05T03:02:35Z

(Both repos are public, in an org account). Our first failure is here (a few hours before quantumfusion's last success): https://github.com/cagov/cannabis.ca.gov/actions/runs/3840800379

peter-evans · 2023-01-05T03:11:38Z

@jbum Thank you. So it looks like the repo for the workflow and where you are creating the pull request is the same. I wonder if the error is being caused because the workflow is triggered by repository_dispatch from a different repository. I noticed that your workflow also can be triggered manually by workflow_dispatch. Please could try manually running the workflow from the GitHub UI. If that works, then it could be a permissions change they have made to the GITHUB_TOKEN regarding being triggered from a different repo.

jbum · 2023-01-05T03:13:08Z

Fwiw, I notice that the call right after "Attempting creation of pull request" is to octokit (which was updated some 7 hours ago, around the time the failures started for us?). We will try that thanks!

jbum · 2023-01-05T03:17:40Z

The manual run also fails (tried it in a different public repo we've been testing on). https://github.com/cagov/odi-publishing-11ty-sandbox/actions/runs/3843544700

peter-evans · 2023-01-05T03:17:57Z

Fwiw, I notice that the call right after "Attempting creation of pull request" is to octokit (which was updated some 7 hours ago, around the time the failures started for us?). We will try that thanks!

Octokit is a library in use by the action. But you are using v4 of the action, the release of which hasn't changed since 28th November last year.
https://github.com/peter-evans/create-pull-request/releases/tag/v4

jbum · 2023-01-05T03:18:27Z

Yes, understood. Don't think this is your issue. But I'm curious if anyone is successfully using the action at this point?

peter-evans · 2023-01-05T03:25:46Z

All my tests are passing, so I think this is a very specific issue. I'm trying to figure out the exact scenario.

Test run from a hour or so ago:
https://github.com/peter-evans/create-pull-request-tests/actions/runs/3843283956

peter-evans · 2023-01-05T03:28:53Z

I forked your test repo, made a few changes to ignore secrets I don't have, and it seems to work.
https://github.com/peter-evans/odi-publishing-11ty-sandbox/actions/runs/3843584226/jobs/6545964628

jbum · 2023-01-05T03:33:32Z

Woah! Trying that.

peter-evans · 2023-01-05T03:36:06Z

I also tried it in an org and that works, too. I don't have any idea what is going on. 🤔
https://github.com/create-pull-request/odi-publishing-11ty-sandbox/actions/runs/3843637176

jbum · 2023-01-05T03:41:25Z

I suspect our token has expired (still fails if I comment out committer). Will continue investigating that. Thank so much for helping us isolate it. You want way above and beyond.

It is curious that a few folks experienced this specific error message today...

peter-evans · 2023-01-05T03:48:48Z

I suspect our token has expired

It looks like you are using the default GITHUB_TOKEN for the repository. That token doesn't expire.
Or have you created a secret in your repository with the exact same name as the default token?

It is curious that a few folks experienced this specific error message today...

That's why I would be surprised if this was just down to token expiration. Please let me know if you solve it.

davereid-pfg · 2023-01-05T04:14:17Z

Are you creating a pull request remotely? (In a repo other than where the workflow is running)

No, it is the same repository.

Is the repo where the workflow runs private?

Yes

Is the remote repo private?

Yes, but also same repository, not remote

What type of token are you using? What scopes?

Generated via Github App using https://github.com/tibdex/github-app-token action.

    permissions:
      contents: write
      pull-requests: write

Are the repos in an org or user account?

An organization account.

davereid-pfg · 2023-01-05T04:15:44Z

The mysterious thing is that several other similar private repositories under the same organization account didn't fail and were just fine, using the exact same workflow (and same Github token generation via Github App). It seems isolated to one repository, I just can't figure out why. All the logs look the same and I cannot find any distinguishing factor in the workflow runs.

chachasikes · 2023-01-05T04:41:20Z

👋🏼 @davereid-pfg
Interesting & mysterious indeed.

We are trying different configurations of setting head_repo - but no luck yet.

jbum · 2023-01-05T04:42:25Z

We're pretty sure it's not the token or committer at this point...

chachasikes · 2023-01-05T04:44:42Z

Not seeing head_repo set anywhere in create-pull-request. It may be a bug coming from octokit.
We are stopping for the night. Will revisit tomorrow.

davereid-pfg · 2023-01-05T04:59:58Z

I just checked out the branch that was created in our workflow via this action locally for the repository and used gh pr create --base main --title "Test" --body "Body" which succeeded so it doesn't seem to me to be an issue with the API or cli at this point.

Becram · 2023-01-05T06:18:34Z

@peter-evans I am having similar issue, my scenario it different than your test case, I checkout a different repo and use the action to create pr into that repo. This might help reproduce the issue

Katz-Tal · 2023-01-05T08:32:27Z

Hey everyone, same issue for me.
I'm using it for fork sync and since today (it runs every day) it's started doing that error
For same-org, cross-repo pulls, 'head_repo' is required: {"resource":"PullRequest","field":"head","code":"invalid"}

akbast · 2023-01-05T09:25:30Z

I am having also the same issue and the same scenario which @davereid-pfg has described. I am using a reusable workflow in all of the private repositories in which this action used and it is configured with a GitHub App. In some of the repositories it suddenly stopped working.

unkali · 2023-01-05T09:37:33Z

I saw the exact same error pop up yesterday during our workflow

matanshk · 2023-01-05T10:04:36Z

Same issue appears in our public repo under our organization

For same-org, cross-repo pulls, 'head_repo' is required: {"resource":"PullRequest","field":"head","code":"invalid"}

peter-evans · 2023-01-05T10:22:41Z

I found this other issue by searching GitHub. It looks related.
interledger/web-monetization-projects#3558

I'm keeping an eye out for similar issues:
https://github.com/search?q=%22For+same-org%2C+cross-repo+pulls%22&type=issues

I haven't had a response from GitHub Support yet.

gm3dmo · 2023-01-05T10:58:33Z

GitHub engineering are now investigating.

gm3dmo · 2023-01-05T11:07:52Z

@peter-evans Changes have been made. Please can you retry and let us know if the behaviour persists.

akbast · 2023-01-05T11:11:01Z

I have tried in one of the failing repositories. It is working again.

Becram · 2023-01-05T11:11:20Z

its working thank you

gm3dmo · 2023-01-05T11:11:45Z

Apologies for the inconvenience.

peter-evans · 2023-01-05T11:12:25Z

@gm3dmo Thank you for the fix!

Katz-Tal · 2023-01-05T11:34:09Z

It was solved, thanks!

clxmstaab · 2023-01-05T12:55:17Z

solved, thanks

davereid-pfg · 2023-01-05T15:11:10Z

Can confirm as well, resolved today without any changes.

jbum · 2023-01-05T15:16:18Z

@chachasikes and I can confirm as well. Working.

jbum · 2023-01-05T15:32:55Z

Thank you everyone who reported this, and @peter-evans for investigating and @gm3dmo for the fix!

peter-evans · 2023-01-06T01:01:19Z

Closing as resolved. Thank you everyone!

littleGnAl · 2023-03-22T17:10:04Z

I'm not very sure if it's the same issue, here's my failed job:
https://github.com/littleGnAl/hoe/actions/runs/4492290785

After I change it to the restful API, it works fine:
https://github.com/littleGnAl/hoe/actions/runs/4492523688

krebemm · 2023-08-23T20:46:45Z

getting same error Validation Failed: {"resource":"PullRequest","field":"head","code":"invalid"}

it has been working all day too...

krebemm · 2023-08-23T22:09:24Z

getting same error Validation Failed: {"resource":"PullRequest","field":"head","code":"invalid"}

it has been working all day too...

it is happening in two of my repos that have been using it for months and just today has ran 4 hrs ago as well. in my third testing repo, it is working as well

krebemm · 2023-08-29T19:01:44Z

following up @peter-evans this is still happening unfortunately, do you have any suggestions?

HarryZ10 · 2024-02-14T18:21:55Z

@krebemm did you get it working?

krebemm · 2024-02-14T18:24:32Z

@HarryZ10 yes but i ended up just using git cli instead of this action, it has been reliable so far.

This comment was marked as outdated.

Sign in to view

peter-evans closed this as completed Jan 6, 2023

peter-evans mentioned this issue Jan 6, 2023

Renovate not working interledger/web-monetization-projects#3558

Closed

littleGnAl mentioned this issue Mar 22, 2023

Validation Failed: {"resource":"PullRequest","field":"head","code":"invalid"} #1763

Closed

andreancardona mentioned this issue May 30, 2023

Release action deploy-packages.yml fails to create PRs to update dependencies for related projects carbon-design-system/carbon#13890

Closed

1 task

PRs fail to create due to Error: For same-org, cross-repo pulls, 'head_repo' is required: {"resource":"PullRequest","field":"head","code":"invalid"} #1459

PRs fail to create due to Error: For same-org, cross-repo pulls, 'head_repo' is required: {"resource":"PullRequest","field":"head","code":"invalid"} #1459

Comments

davereid-pfg commented Jan 4, 2023 • edited Loading

Subject of the issue

Steps to reproduce

yktakaha4 commented Jan 5, 2023

chachasikes commented Jan 5, 2023 • edited Loading

chachasikes commented Jan 5, 2023

peter-evans commented Jan 5, 2023

This comment was marked as outdated.

jbum commented Jan 5, 2023

quantumfusion commented Jan 5, 2023

peter-evans commented Jan 5, 2023

peter-evans commented Jan 5, 2023

chachasikes commented Jan 5, 2023

jbum commented Jan 5, 2023 • edited Loading

peter-evans commented Jan 5, 2023

jbum commented Jan 5, 2023

jbum commented Jan 5, 2023

peter-evans commented Jan 5, 2023

jbum commented Jan 5, 2023 • edited Loading

peter-evans commented Jan 5, 2023

peter-evans commented Jan 5, 2023

jbum commented Jan 5, 2023

peter-evans commented Jan 5, 2023

jbum commented Jan 5, 2023 • edited Loading

peter-evans commented Jan 5, 2023 • edited Loading

davereid-pfg commented Jan 5, 2023 • edited Loading

davereid-pfg commented Jan 5, 2023 • edited Loading

chachasikes commented Jan 5, 2023

jbum commented Jan 5, 2023

chachasikes commented Jan 5, 2023 • edited Loading

davereid-pfg commented Jan 5, 2023

Becram commented Jan 5, 2023 • edited Loading

Katz-Tal commented Jan 5, 2023

akbast commented Jan 5, 2023

unkali commented Jan 5, 2023

matanshk commented Jan 5, 2023

peter-evans commented Jan 5, 2023

gm3dmo commented Jan 5, 2023

gm3dmo commented Jan 5, 2023

akbast commented Jan 5, 2023

Becram commented Jan 5, 2023

gm3dmo commented Jan 5, 2023

peter-evans commented Jan 5, 2023

Katz-Tal commented Jan 5, 2023

clxmstaab commented Jan 5, 2023

davereid-pfg commented Jan 5, 2023

jbum commented Jan 5, 2023

jbum commented Jan 5, 2023

peter-evans commented Jan 6, 2023

littleGnAl commented Mar 22, 2023

krebemm commented Aug 23, 2023

krebemm commented Aug 23, 2023

krebemm commented Aug 29, 2023

HarryZ10 commented Feb 14, 2024

krebemm commented Feb 14, 2024

davereid-pfg commented Jan 4, 2023 •

edited

Loading

chachasikes commented Jan 5, 2023 •

edited

Loading

jbum commented Jan 5, 2023 •

edited

Loading

jbum commented Jan 5, 2023 •

edited

Loading

jbum commented Jan 5, 2023 •

edited

Loading

peter-evans commented Jan 5, 2023 •

edited

Loading

davereid-pfg commented Jan 5, 2023 •

edited

Loading

davereid-pfg commented Jan 5, 2023 •

edited

Loading

chachasikes commented Jan 5, 2023 •

edited

Loading

Becram commented Jan 5, 2023 •

edited

Loading