New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEAT]: Support overriding github api url #77
Comments
|
We pretty much implement the same thing as |
|
@gr2m Isn’t this already supported? The action reads an environment variable named |
|
I think @harshtrivedi134 is asking to pass a custom GitHub API URL which is different from the one configured in the Action, in order to access an organization on a different server? |
That's correct. In my case, I am trying to run the workflow in a github.com repo and the Github app is installed in an organization in Github Enterprise. |
|
This is a hard blocker from our team using this action. A long time ago I filed a ticket for this in tibdex's version of the action. Support is nearly trivial to add and this would allow us to migrate our use to this action. |
|
I started a PR here, can y'all have a look? #88. Tests still need fixing and I'll add a test specific to the new option, but otherwise this should be good to go |
originally posted by @harshtrivedi134 at octokit/octokit.js#2569
Describe the need
Reference from discussion
I was creating an access token for a github app installed in a different organization and repository. I learned about https://github.com/actions/create-github-app-token#create-a-token-for-all-repositories-in-another-owners-installation.
Similar to the
baseUrloption in Octokit constructor, it would be great if we could specify the github API url as an input to this actionI tried creating an access token for my github app installed in a different organization by specifying the owner and repository using the following:
However, the default github API hostname/url is set to
api.github.comand we cannot change it to a custom hosted github installation.Code of Conduct
The text was updated successfully, but these errors were encountered: