Authenticating with git extraheader causes error, possibly in combination with Git LFS about create-pull-request HOT 5 CLOSED

Thanks for investigating! And thanks for the great package you've written - super useful ^_^

from create-pull-request.

@mimecuvalo This should now be fixed in the latest release.

My test case for this creates an LFS tracked file and it is successfully pushed to a branch.

      - name: Create LFS tracked file
        run: |
          git lfs track "*.dat"
          date +%s > large_file.dat
      - name: Create Pull Request
        uses: peter-evans/create-pull-request@v2
        with:
          token: ${{ secrets.GITHUB_TOKEN }}

from create-pull-request.

@mimecuvalo Thank you for raising this issue. This is interesting because 289fda9 was an attempt to copy how the official actions/checkout action handles authentication.

I've found Git LFS tests that strongly suggest it does work with extraheader so it looks fixable. I will try to reproduce this problem in a workflow.

It would be helpful if you could provide a more complete workflow to help me reproduce this.

from create-pull-request.

I've discovered that this is a possible bug with Git LFS itself.
Created this issue to report my findings: git-lfs/git-lfs#4031

For now, please version pin to v2.4.1.

      - name: Create Pull Request
        uses: peter-evans/[email protected]
        with:
          token: ${{ secrets.GITHUB_TOKEN }}

from create-pull-request.

Thanks for fixing it so fast! I was following the discussion on the other bug - was great to see the git-lfs team being so responsive, too :)

from create-pull-request.