error: remote fork already exists.

[shrinktofit]

Subject of the issue

Use push-to-fork option, build twice, the error should appear:

Run peter-evans/create-pull-request@v4
  with:
    path: engine-extensions
    push-to-fork: shrinktofit/engine-extensions
    token: ***
    title: Bump @editor/fbx-gltf-conv to 1.0.0-alpha.4[3](https://github.com/shrinktofit/cocos-editor/actions/runs/4228727838/jobs/7344440203#step:6:3)(editor patch: 5[4](https://github.com/shrinktofit/cocos-editor/actions/runs/4228727838/jobs/7344440203#step:6:4)8489468)
    body: 这个 PR 希望更新 FBX-glTF-conv 依赖为  1.0.0-alpha.43，包内版本为：[5](https://github.com/shrinktofit/cocos-editor/actions/runs/4228727838/jobs/7344440203#step:6:5)484894[6](https://github.com/shrinktofit/cocos-editor/actions/runs/4228727838/jobs/7344440203#step:6:6)8。
  
    add-paths: packages/fbx-gltf-conv/*
  
    commit-message: [create-pull-request] automated change
    committer: GitHub <noreply@github.com>
    author: shrinktofit <shrinktofit@users.noreply.github.com>
    signoff: false
    branch: create-pull-request/patch
    delete-branch: false
    draft: false
  
(node:4[7](https://github.com/shrinktofit/cocos-editor/actions/runs/4228727838/jobs/7344440203#step:6:7)60) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
Save persisted git credentials
  "C:\Program Files\Git\cmd\git.exe" config --local --name-only --get-regexp http.https://github.com/.extraheader ^AUTHORIZATION:
  http.https://github.com/.extraheader
  "C:\Program Files\Git\cmd\git.exe" config --local --get-regexp http.https://github.com/.extraheader ^AUTHORIZATION:
  http.https://github.com/.extraheader AUTHORIZATION: basic ***
  "C:\Program Files\Git\cmd\git.exe" config --local --unset http.https://github.com/.extraheader ^AUTHORIZATION:
  Unset config key 'http.https://github.com/.extraheader'
Determining the base and head repositories
  "C:\Program Files\Git\cmd\git.exe" config --local --get remote.origin.url
  https://github.com/cocos/engine-extensions
  Checking if 'shrinktofit/engine-extensions' is a fork of 'cocos/engine-extensions'
  "C:\Program Files\Git\cmd\git.exe" remote add fork https://github.com/shrinktofit/engine-extensions
  error: remote fork already exists.
  Error: The process 'C:\Program Files\Git\cmd\git.exe' failed with exit code 3
Restore persisted git credentials
  "C:\Program Files\Git\cmd\git.exe" config --local --name-only --get-regexp http.https://github.com/.extraheader ^AUTHORIZATION:
  "C:\Program Files\Git\cmd\git.exe" config --local http.https://github.com/.extraheader "AUTHORIZATION: basic ***"
  Persisted git credentials restored

Steps to reproduce

# The step
- name: Create Pull Request on editor repository
        uses: peter-evans/create-pull-request@v4
        with:
          path: 'cocos-editor'
          push-to-fork: ${{github.event.inputs.editor_pr_repo}}
          token: ${{secrets.PUBLISH_FBX_GLTF_CONV_ON_NPM_REPO_TOKEN}}
          title: '更新对 @editor/fbx-gltf-conv 的依赖到 ${{github.event.inputs.main_bump_version}}(editor patch: ${{github.event.inputs.editor_patch_bump_version}})'
          add-paths: |
            app/package.json
          body: |
            这个 PR 更新对 npm 包 @editor/fbx-gltf-conv 的依赖，相关 PR：${{ steps.create_package_update_pr.outputs.pull-request-url }}。

[peter-evans]

Hi @shrinktofit

Are you trying to call the action twice during the same job? Please could you share the full workflow.

[TravisEz13]

I'm hitting this too. In my case, the branch is left over from a previous PR. I cannot share the workflow. Here is the last PR that was created: PowerShell/PowerShell#19459

I'm using 4.2.3. I'm trying 5.0.0

Update: I think my issue was that a branch of the same name also existed in the upstream (origin by the remote naming here).

 "C:\Program Files\Git\bin\git.exe" checkout --progress update-cgmanifest --
  hint: If you meant to check out a remote tracking branch on, e.g. 'origin',
  hint: you can do so by fully qualifying the name with the --track option:
  hint: 
  hint:     git checkout --track origin/<name>
  hint: 
  hint: If you'd like to always have checkouts of an ambiguous <name> prefer
  hint: one remote, e.g. the 'origin' remote, consider setting
  hint: checkout.defaultRemote=origin in your config.
  fatal: 'update-cgmanifest' matched multiple (2) remote tracking branches
  Error: The process 'C:\Program Files\Git\bin\git.exe' failed with exit code 128

[peter-evans]

Hi @TravisEz13

I think your issue might be slight different. Thank you for reporting it.
Did you find a workaround, or is the workflow consistently failing?

I found this PR where you've copied workflows to a private repo. I noticed that in daily.yml the update-tpn and update-cgmanifest jobs are both executing create-pull-request with branch: update-cgmanifest. Perhaps the update-tpn job should target a different branch name like branch: update-tpn to avoid any conflict. I'm not sure if that is the issue here, but just thought I would mention it in case that is the cause.

Does the private repo where you have moved daily.yml too also contain a branch called update-cgmanifest? I wonder if that is confusing the action because perhaps update-cgmanifest matches a remote tracking branch in the local private repo and the fork (pwshBot/PowerShell).

[TravisEz13]

I wonder if that is confusing the action because perhaps update-cgmanifest matches a remote tracking branch in the local private repo and the fork (pwshBot/PowerShell).

It was the public repo that contained the branch called update-cgmanifest, and that is what was confusing the action. The public repo used to run the workflow and I didn't clean it up when I move the workflow to the private repo. The private repo is only used to host the workflows. They still clone and open the PR against the public repo.

I don't think the two jobs using the same branch was causing an actual problem, but I have a PR in the private repo to fix the issue.

BTW, thanks for responding. My issue is resolved, but I thought I would document the issue I was facing.

[peter-evans]

Hi @shrinktofit

Sorry it took me so long to look into this issue. I've made change that I think will fix your issue and added it to the v6 release candidate. You can use it like this:

      - uses: peter-evans/create-pull-request@v6-rc

I'll be releasing v6 at some point in the near future.

[shrinktofit]

Really appreciate it @peter-evans

[peter-evans]

I've now released v6. Thanks for your patience.