The endpoint encapsulates portions of the GitHub API, relying on the org.eclipse.egit.github.core Java SDK. Available endpoint URIs include: CONSUMERS github://pullRequest (new pull requests) github://pullRequestComment (new pull request comments) github://commit/[branch] (new commits) github://tag (new tags) PRODUCERS github://pullRequestComment (create a new pull request comment; see PullRequestCommentProducer for header requirements) The endpoints will respond with org.eclipse.egit.github.core-provided POJOs (PullRequest, CommitComment, RepositoryTag, RepositoryCommit, etc.) Note: Rather than webhooks, this endpoint relies on simple polling. Reasons include: - concerned about reliability/stability if this somehow relied on an exposed, embedded server (Jetty?) - the types of payloads we're polling aren't typically large (plus, paging is available in the API) - need to support apps running somewhere not publicly accessible where a webhook would fail
Name | Kind | Type | Required | Deprecated | Default Value | Enum Values | Description |
---|---|---|---|---|---|---|---|
type | path | org.apache.camel.component.github.GitHubType | false | CLOSEPULLREQUEST PULLREQUESTCOMMENT COMMIT PULLREQUEST TAG PULLREQUESTSTATE PULLREQUESTFILES GETCOMMITFILE |
|||
branchName | path | java.lang.String | false | ||||
username | parameter | java.lang.String | false | ||||
password | parameter | java.lang.String | false | ||||
oauthToken | parameter | java.lang.String | false | ||||
repoOwner | parameter | java.lang.String | false | ||||
repoName | parameter | java.lang.String | false | ||||
state | parameter | java.lang.String | false | ||||
targetUrl | parameter | java.lang.String | false | ||||
encoding | parameter | java.lang.String | false | ||||
exchangePattern | parameter | org.apache.camel.ExchangePattern | false | InOnly | InOnly RobustInOnly InOut InOptionalOut OutOnly RobustOutOnly OutIn OutOptionalIn |
Sets the default exchange pattern when creating an exchange | |
synchronous | parameter | boolean | false | false | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). |