Avoid resetting the branch to remote

[zchenyu]

My workflow is as follows

1. Checkout workflow branch (usually main, but sometimes some working branch)
2. Make local changes (uncommitted) to working branch
3. Run peter-evans/create-pull-request@v6 with local changes
4. Do additional stuff with local changes

However I noticed that when create-pull-request runs, it resets the working base branch:

  Resetting working base branch 'xxx'
  /usr/bin/git checkout --progress xxx --
  Switched to branch 'xxx'
  Your branch is up to date with 'origin/xxx'.
  /usr/bin/git reset --hard origin/xxx
  HEAD is now at xxxxxxxx commit

Is there a way to disable or workaround this?

[shahzore-qureshi-usmobile]

Yes please!! I just discovered this issue. Any idea to not do this??? Thanks!

[peter-evans]

Hi @zchenyu

Is there a way to disable or workaround this?

I'm afraid not. I can't remember the details off the top of my head, but I'm confident that this was something I decided to do very intentionally.

To workaround this, you can just checkout the pull request branch again in a step after the action completes.

[shahzore-qureshi-usmobile]

Thanks Peter! Your workaround is working great. Having said that, would you be open to adding a warning to the docs mentioning that any changes will be "lost" or "reverted" after this GitHub action is run? That way, more people are better informed on how this action works and can avoid debugging complex issues like figuring out why their Android APK is lacking new changes. Thanks in advance!