Community
Participate
Working Groups
We're going to need REST API for git remote (tracking remote branches).
Browsing remotes added in http://git.eclipse.org/c/e4/org.eclipse.orion.server.git/commit/?id=007b7f48713fcb026ca2d0a76e9c2d561940e04e.
I've got a question about existing part of this REST API: GET /git/remote/{remote_name}/file/{project} Response contains some information about remote and ALL branches in the repository ('children' section). So, i.e. when I send request for remote "test", children section contains branch refs/remotes/origin/master. Is it correct behaviour or a bug?
Early version ready for review (remote add and remote rm).
(In reply to comment #2) > [...] when I send request for remote "test", > children section contains branch refs/remotes/origin/master. Is it correct > behaviour or a bug? This is expected. We give brief info about remote branches when asking about branch. The user can then fetch details about a branch by following BranchLocation.
Piotrek I would rather use: (1) POST /git/remote/file/[path]/ { Name: remoteName URL: remoteURL ... } instead of: (2) PUT /git/remote/[remoteName]/file/[path]/ The reason is, we have (1) already when we try to create a new remote and we would have to craft (2) manually to send PUT for it.
I released changes to the server code. We still need tests and our wiki with Git REST API updated. When these two things are done, we may close the bug.
Git REST API is updated. Tests and fixes: https://github.com/pjanik/orion.server/tree/bug339109update1 [I wrote all this code and have the rights to contribute it to Eclipse under the eclipse.org web site terms of use]
Piotrek, please take a look at bug 347906.
Tests added with 1652ad0af262a8b383222b9195666b363673663f.