Brett E. Meyer created CAMEL-7777:
-------------------------------------
Summary: GitHub component
Key: CAMEL-7777
URL: https://issues.apache.org/jira/browse/CAMEL-7777
Project: Camel
Issue Type: New Feature
Reporter: Brett E. Meyer
For Overlord (projectoverlord.io), we need to consume "events" from GitHub, as
well as produce "actions". We're moving towards using Camel as a backbone for
various capabilities, and as such are writing the endpoint functionality as new
Camel components. I'd love to see this incorporated as another mainline Camel
component.
Work in progress:
https://github.com/brmeyer/camel-github
Consumer ideas:
github://pullRequest (new pull requests)
github://pullRequestComment (new pull request comments)
github://commit/[branch] (new commits)
github://tag (new tags)
Producer ideas:
github://pullRequestComment/[pr #]
Obviously, that's only a small portion of the capabilities. The GitHub API is
extensive and opens a large variety of possibilities.
It uses the org.eclipse.egit.github.core SDK
(https://github.com/eclipse/egit-github/tree/master/org.eclipse.egit.github.core),
which is a part of Mylyn and licensed under the EPL. So, there shouldn't be
any reason why this would need to be restricted to Camel Extras.
Similar to what I did for camel-twitter, the Exchange payloads would be the
SDK-provided objects themselves (PullRequest, CommitComment, RepositoryTag,
RepositoryCommit, etc.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
