Hi @salexander6

Thank you for identifying this issue. I'm interested to know how this occurs so I can reproduce it. Please could you show me a workflow that results in this happening. Perhaps you are not using the official actions/checkout action to checkout the repository?

Please could you show me a workflow that results in this happening. Perhaps you are not using the official actions/checkout action to checkout the repository?

The repo is private but here's the relevant workflow section

steps:
  - name: Check out 99spokes/data
    run: |
      git clone --filter=blob:none --no-checkout https://$BOT_GITHUB_TOKEN@github.com/99spokes/data.git
      cd data
      git sparse-checkout init --cone --sparse-index
      git sparse-checkout set products
      git checkout main
    env:
      BOT_GITHUB_TOKEN: ${{ secrets.BOT_GITHUB_TOKEN }}

  - name: Download artifacts
    uses: actions/download-artifact@v2
    with:
      name: products
      path: data/products

  - name: Create Pull Request
    uses: 99spokes/create-pull-request@fix-https-repository-name
    with:
      path: data
      token: ${{ secrets.BOT_GITHUB_TOKEN }}
      branch: update-products
      commit-message: Update products.
      title: 'Update Products'
      labels: automerge

Adding this here has me wondering if cloning without the .git extension would work around the issue 🤔

Ok, it makes sense now. Not using the official checkout action causes the remote URL to include the .git suffix. It's an easy fix though, so I'm happy to get this merged, regardless of whether or not you are able to work around it.

/test repository=99spokes/create-pull-request ref=fix-https-repository-name build=true

Command run output

Thank you!

Released as v4.0.1 / v4

Thanks for the great action!