Community
Participate
Working Groups
The CLI from org.eclipse.jgit.pgm is pretty cool, but seems to be a little bit out dated comparing to JGit API from org.eclipse.jgit. After a quick look I've noticed couple of places where the API is not used or where having the API already in place a CLI command could be added: * org.eclipse.jgit.api.ListTagCommand > org.eclipse.jgit.pgm.Tag, see http://egit.eclipse.org/r/#change,4718 * org.eclipse.jgit.api.CloneCommand > org.eclipse.jgit.pgm.Clone * org.eclipse.jgit.api.PullCommand > org.eclipse.jgit.pgm.Pull (doesn't exist) * org.eclipse.jgit.api.RebaseCommand > org.eclipse.jgit.pgm.Rebase (doesn't exist) * ... This kind of feedback could not only make the CLI more robust, but it could also work the other way round making sure the API supports all args needed be the CLI.
org.eclipse.jgit.api.StatusCommand > org.eclipse.jgit.pgm.Status (doesn't exist, see bug 348318)
* cannot find a CLI command for getting and setting repo/global options (org.eclipse.jgit.pgm.Config?)
(In reply to comment #2) > * cannot find a CLI command for getting (...) repo/global options It's https://git.eclipse.org/r/#/c/4898/
See also https://git.eclipse.org/r/#/c/5763/ for adding --all switch to org.eclipse.jgit.pgm.Commit.
See also https://git.eclipse.org/r/#/c/5764/ for printing out which branch has been checked out in org.eclipse.jgit.Checkout
JGit Init command does not support specifying the directory for the new repository (but InitCommand in the api does). For example: jgit init my_new_repo returns: fatal: No argument is allowed: my_new_repo You have to create the new directory manually, and the executing "jgit init" from there.
(In reply to comment #6) > JGit Init command does not support specifying the directory for the new > repository (but InitCommand in the api does). Filed bug 380117 for this. It should be easy to fix.
