camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett E. Meyer (JIRA)" <>
Subject [jira] [Commented] (CAMEL-7777) GitHub component
Date Tue, 30 Sep 2014 17:44:35 GMT


Brett E. Meyer commented on CAMEL-7777:

Hey guys, created an additional pull request to add a new producer: automatically close a
pull request.  There were a few additional cleanup items.

> GitHub component
> ----------------
>                 Key: CAMEL-7777
>                 URL:
>             Project: Camel
>          Issue Type: New Feature
>            Reporter: Brett E. Meyer
>            Assignee: Willem Jiang
>             Fix For: 2.15.0
> For Overlord (, 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:
> 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 (,
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

View raw message