Pass the `token` to `sticky-pull-request-comment`

[ItsDrike]

Currently, when I specify the token for this action, it is only used for pushing to the repo, however, I would also like to use this token to make the comment with (e.g. to pass it over to marocchino/sticky-pull-request-comment action too).

I have a custom github app and I prefer it to comment on my PRs, instead of it showing up as a comment from the github-actions bot. It also allows me to restrict GITHUB_TOKEN permissions in the workflow and only grant this app permissions to comment on PRs / push to the repo.

I'm not sure if you'd consider this a breaking change for users that don't expect the token they provided to also be used to make the sticky comment, if you would, then perhaps instead add another input for the action, e.g. commentToken to be used for this purpose.

---

The only way around this currently is to disable the sticky comment and handle sending it manually.

[rossjrw]

You're right that using the token would be a breaking change seeing as that token could well be authenticated for a different repository to the one that the comment is being posted in. The comment-token solution is probably the better approach; in your case you'd be specifying the same token twice.

That being said, what you did in your linked implementation is correct in principle, in that the default comment can be disabled to let you do whatever you want with a custom comment, including sending it using a different token. It would be my recommended solution.

I'm not sure that faithfully reproducing marocchino/sticky-pull-request-comment's parameters in this action is a good idea, even if it's just one of them that this issue is about. I'll have to consider how complicating this action's usage balances against the utility. Seeing as the current behaviour is effectively accidental, I'll leave this issue open to mull it over.