-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Better Github Integration #91
Comments
COMPLETELY agree about read/write. Been needing this for a while. It was actually the reason I started Dillinger years ago. I would recommend having a go at it. At the time in the past, the Github API wasn't super clear on straightforward ways of committing back to them via the API. Probably much better now. This would be an epic pull request. |
Actually, after checking out https://github.com/michael/github We should actually rewrite the |
yeah if I was versed in javascript at all, id make a PR. but im a Java guy. |
This is such a great project. Thanks Joe! The only thing I'd like to request is support for Gists (importing/creating). |
@kevinSuttle agree 100%. We need to refactor the Github backend piece overall to close the loop (push changes to repo) and post to Gists. Not super hard, but oh the time needed!! |
I totally get it. I'd do it myself if I had the time... |
It seems everything from the original request has been implemented:
I have made a more specific request for a custom commit message at: #208 I propose that API refactoring discussion be moved to another issue and this be closed. BTW: for some reason https://github.com/prose/prose stopped using michael/github, which was originally designed for Prose I think, they now hardcode URLs: github-tools/github#68 (comment) Another option of API wrapper is https://github.com/philschatz/octokit.js, forked from michael/github and promise based, made in the context of https://github.com/oerpub/github-bookeditor |
support for Github flavored markdown.
see #12
It would be great if we could switch out the markdown parser via a radio button or something when using dillinger to parse it as github flavored vs normal flavored. I have found this, which may help.
https://github.com/isaacs/github-flavored-markdown
It references another markdown parsing library that you guys may or may not have heard of, or might even be using in this project.
support for committing changes to github repos
Currently, Dillinger requests access to read and write to github repositories for its integration. It would be VERY nice if we could write the file in dillinger, and have dillinger commit that file back to the repo with a canned or provided commit message.
this would be found useful: https://github.com/michael/github
The text was updated successfully, but these errors were encountered: