[Feature] Be able to specify GitHub user override

[IvanLH]

The action currently hardcodes the GitHub user to be associated with the Token specified on the environment. However, if a user wanted to create the PR as a different user this would block them.

A field could be added to specify a user name override to fix this issue.

[breadadams]

We're using the pre-existing setupGitUser option, and that is setting both the PR author and the committer. Doesn't that resolve the problem?

[IvanLH]

We're using the pre-existing setupGitUser option, and that is setting both the PR author and the committer. Doesn't that resolve the problem?

It's been a while, but I don't think so, on the related PR #443 I make the change and the GitHub user is hard coded into one of the scripts, concretely the one that creates the release PRs.

[breadadams]

It's been a while, but I don't think so, on the related PR #443 I make the change and the GitHub user is hard coded into one of the scripts, concretely the one that creates the release PRs.

Yeah np, I just happened to spot the issue when reporting something else and thought I'd provide my 2 cents :)

I saw line that, however I'm not sure why you'd need to introduce a new input if there's already a setupGitUser. Might be something different from your setup but like I mentioned, we have a custom PR author, etc just from using this.

If anything needs changing here I'd argue that it'd be to use the existing setupGitUser output on the line you've touched, defaulting to the current github-actions[bot] (as opposed to adding a new option):

action/src/index.ts

Line 43 in 04d574e

`machine github.com\nlogin github-actions[bot]\npassword ${githubToken}`

[bluwy]

While I think the .netrc part is strange, you can already specify a different user like this: https://github.com/bombshell-dev/automation/blob/fefdda5cafd503bf3caaccd0a350c5d863d4289c/.github/workflows/publish.yml#L74-L77

I think this should resolve the issue without needing a new option. However, we should revisit .netrc again. (There's open issues tracking this)