feat: add force option to tryFetch

[leeopop]

The problem

Dockerized self-hosted runner (https://github.com/myoung34/docker-github-actions-runner) does not reset its local storage when a task is finished.

Thus, a newly created PR via worker#5 cannot be fetched via worker#7 because its not a fast-forward change.

This makes the later hasDiff logic that stops pushing if the actual content has no difference (the commit hashes are different because the commit has different createdAt timestamp.

[PR Log]

[Action Log]

[Actual diff between two consequent pushes]

Solution

Adding force option to git.fetch will overwrite previously cached branch information.

Justification

I found that all four git.fetch command in create-or-update-branch.ts already has the force option except the one changed in this PR.

Alternatives

I may add manual rm -rf /working/.git command before all self-hosted actions, but the above justification makes this solution more desirable.

[peter-evans]

/test repository=leeopop/create-pull-request ref=feature/force-fetch build=true

Command run output

[peter-evans]

Hi @leeopop

Thank you for contributing.

I think adding --force to that fetch should be fine. I can't think of any potential issues.

[peter-evans]

Released as v4.0.4 / v4.

Thank you!