Skip to content

Configurable github endpoint to support publishing gists to Github Enterprise#1364

Merged
juhasch merged 1 commit intoipython-contrib:masterfrom
shiti-saxena:master
Dec 31, 2018
Merged

Configurable github endpoint to support publishing gists to Github Enterprise#1364
juhasch merged 1 commit intoipython-contrib:masterfrom
shiti-saxena:master

Conversation

@shiti-saxena
Copy link
Copy Markdown
Contributor

@shiti-saxena shiti-saxena commented Oct 23, 2018

Added an additional property github_endpoint which will be used to publish gists. If not set, the endpoint is https://github.com

@shiti-saxena shiti-saxena changed the title [gist-it] Making github endpoint configurable to support publishing gists to Github Enterprise [gist-it] Configurable github endpoint to support publishing gists to Github Enterprise Oct 23, 2018
@shiti-saxena
Copy link
Copy Markdown
Contributor Author

@jcb91 do you think this might be useful?

@shiti-saxena shiti-saxena changed the title [gist-it] Configurable github endpoint to support publishing gists to Github Enterprise Configurable github endpoint to support publishing gists to Github Enterprise Nov 6, 2018
@juhasch
Copy link
Copy Markdown
Member

juhasch commented Dec 31, 2018

Thank you. Looks good to me.

@juhasch juhasch merged commit a64846d into ipython-contrib:master Dec 31, 2018
@DThielke
Copy link
Copy Markdown

While helpful, this is not quite configurable enough in my case.

The url for the gist api on github.com itself is https://api.github.com/gists/. However, my company's enterprise server uses the format https://hostname/api/v3/gists/. According to https://developer.github.com/enterprise/2.16/v3/enterprise-admin/, this is the default enterprise configuration.

It would be great if the configuration allowed for this kind of flexibility instead of only customizing the host name.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants