Add support for using action with Github Enterprise server

[steve21168]

This allows this action to work with GHES instance whose api url is not the public github.com domain.

[dscho]

@steve21168 thank you for your contribution!

[dscho]

Great! This also addresses the infrequent problem I encountered recently where rate limiting of GitHub hosted build agents kicked in due to other workflows issuing unauthenticated API requests.

[mxschmitt]

(I think by default GitHub Actions does not pass the GITHUB_TOKEN into the GitHub Action - the user would have to manually pass it over)

[dscho]

(I think by default GitHub Actions does not pass the GITHUB_TOKEN into the GitHub Action - the user would have to manually pass it over)

I think you are right. But we can use this trick instead of requiring the user to manually specify it.

I'll whip up a PR.

[mxschmitt]

cool we should also wire it up with brew I think: #69 (comment)

[dscho]

cool we should also wire it up with brew I think: #69 (comment)

Good point. I opened #150 and will augment it accordingly.

[dscho]

@mxschmitt augmented.

[steve21168]

So I tested this on my teams GHES and the token was available via the process.env call . I had originally implemented this via passing the token and then realized it could be simpler.

According to the docs github context has the token:
https://docs.github.com/en/actions/learn-github-actions/contexts#github-context

So at the least I think you could do this:

...
with:
  github-token: ${{ github.token }}

[steve21168]

Okay I see we added:

    default: ${{ github.token }}

Nice! That's even better. It's great when the user doesn't even have to be aware of the difference in where they're running the action.

[dscho]

@mxschmitt I rebased and force-pushed this PR branch on top of #150 to avoid merge conflicts.