Support local Git servers #21

Open cxj opened 7 years ago

A lot of companies (e.g. mine) don't store their source code on GitHub, GitLab or BitBucket, but rather use Gitolite, Gerrit or just a plain SSH Git repo clone as a central hub.

How hard would it be to add support for those kinds of Git servers? Would it be within the scope of this project?

It would definitely be in the scope of this project.

Would this implementation be adding a src/Api/Generic.php that extends AbstractApi?

@svpernova09 Maybe? In any case, I am contemplating changes that will warrant a 3.0 release, so now is the time (if you or @cxj have the inclination) to start working up a proof of concept.

@cxj @svpernova09 I have begun on the 3.x branch to incorporate pds/skeleton research results. If you're still interested in submitting PRs related to this issue, now would be the time.

I've got some preliminary code working for generic Git repositories reached via SSH. It has a couple of limitations:

Since a Git repo has no concept of issue tickets, the API issues method is pretty much a no-op. This is where someone could connect code to an issue tracker, such as Redmine, Bugzilla, JIRA, Trac, etc.
The concept of a release in this usage is really user specific. Some users might simply use an annotated tag on master to indicate a release. Others might have multiple branches, e.g. development, staging, release, to which releases need to merge and migrate. Hence, my current code simply tags the current branch in method release.

See PR #26.

producerphp / producer.producer

Support local Git servers #21