We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
where SECRETHOSTNAME should be a variable or something.
SECRETHOSTNAME
def initialize(user, pass, repo) @user = user $logger.debug("#{@user} connects to github repo '#{repo}'") + Octokit.configure do |c| + c.api_endpoint = "https://SECRETHOSTNAME/api/v3/" + end
details: https://github.com/octokit/octokit.rb#working-with-github-enterprise
The text was updated successfully, but these errors were encountered:
also in enterprise mode, I had to comment out rate_check because apparently rate checks aren't enterprisey.
rate_check
Sorry, something went wrong.
It looks like the best way to support this is simply via an api_endpoint variable in the configuration file, where the default is standard github.
api_endpoint
If you you provide a PR for this, I'll merge it right away.
Ok thanks.
Enviado desde nuestro iPhone.
El ago 29, 2016, a las 10:33 AM, Matthias Vallentin [email protected] escribió: It looks like the best way to support this is simply via an api_endpoint variable in the configuration file, where the default is standard github. If you you provide a PR for this, I'll merge it right away. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
El ago 29, 2016, a las 10:33 AM, Matthias Vallentin [email protected] escribió:
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
No branches or pull requests
where
SECRETHOSTNAME
should be a variable or something.details: https://github.com/octokit/octokit.rb#working-with-github-enterprise
The text was updated successfully, but these errors were encountered: