Skip to content
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

Support Gitlab API #68

Closed
edrex opened this issue Jul 15, 2013 · 15 comments
Closed

Support Gitlab API #68

edrex opened this issue Jul 15, 2013 · 15 comments

Comments

@edrex
Copy link

edrex commented Jul 15, 2013

This is a placeholder issue to create a version of Github.js which works with Gitlab's HTTP API. The motivation is to allow Prose.io to work with self-hosted repos using Gitlab.

Gitlab is an opensource/self-hostable alternative to Github. It has a very similar data model (users, orgs, forks, etc), and an HTTP API of similar expressivity.

There is a public service at https://gitlab.com/ for testing.

Any other interest in such a port?

@philschatz
Copy link
Contributor

I'm interested in both having a port and contributing (see https://github.com/philschatz/octokit.js and https://github.com/philschatz/github-book)

@elviejo79
Copy link

This would be very useful... count me in for testing :-)

@elumalai
Copy link

+1

1 similar comment
@walterjenner
Copy link

+1

@sebble
Copy link

sebble commented May 12, 2014

Has there been further discussion on this issue?

I had a quick look at the HTTP API referenced in the original comment and noticed a NodeJS implementation which may provide some of the groundwork.

@philschatz
Copy link
Contributor

I skimmed through moul/node-gitlab the design choices look very similar to https://github.com/philschatz/octokat.js . I think I can hack something up once I finish the following:

  • re-add in a few helper methods (like repo.writeMany())
  • add support for callbacks instead of just promises
  • write tests for all the new methods in the PR

Aside: philschatz/octokit.js no longer depends on jQuery and underscore but it does use Promises and CoffeeScript.

@cirosantilli
Copy link

+1. Is Prose currently using this project? Couldn't find where it is required.

@philschatz
Copy link
Contributor

The original library is a fork of the lib used by Prose.

octokat.js uses a Regular Expression (see src/grammar.coffee) to define what operations are possible.

Does anyone have a list of all routes for GitLab's API?

@cirosantilli
Copy link

@philschatz Not sure there is a list, but a good approximation can be found with:

git clone https://github.com/github/developer.github.com
cd developper.github.com/content/v3
git grep -E '^\s*(HEAD|GET|POST|PATCH|PUT|DELETE) /'

@cirosantilli
Copy link

I have started sketching a solution at philschatz#59 to see how feasible this is.

@sebble
Copy link

sebble commented Jun 23, 2014

@philschatz I used the command suggested by @cirosantilli to produce the following files https://gist.github.com/sebble/ed1bf6a723ac8fee8cf1, I am also looking into GitLab support with Prose which seems not to use a library any more unless I am mistaken, see prose/prose#713.

@mikemorris
Copy link
Contributor

For reference, Prose has not used this library for almost a year now.

@cirosantilli
Copy link

@sebble This is very interesting!

  1. is there a particular reason you are interested in a GitLab editor frontend? I'm building: https://github.com/booktree/booktree
  2. the file prose.io of the Gist:
    1. contains all GitHub entry points?
    2. GitLab support added is partial or full currently?

@sebble
Copy link

sebble commented Jun 24, 2014

Thanks, see prose/prose#713 for prose GitHub/GitLab/Prose discussion.

@aendra-rininsland
Copy link
Member

I'd really like to close this issue TBTH; the goal of this library is to be a light implementation of the GitHub API, and I'm sure there are much better libraries for interacting with GitLab than this.

If anyone is disappointed that I've done this, please make yourselves heard and I'll consider reopening. Many thanks!

clayreimann added a commit that referenced this issue May 12, 2016
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

No branches or pull requests

9 participants