vcs.github
Introduction
The tags beginning with vcs.github identify events generated by GitHub.
Valid tags and data tables
The full tag must have 4 levels. The first two are fixed as vcs.github. The third level identifies the type of events sent, and the fourth level indicates the event subtype.
Technology | Brand | Type | Subtype |
---|---|---|---|
vcs | github |
|
|
These are the valid tags and corresponding data tables that will receive the parsers' data:
Tag | Data table |
---|---|
vcs.github.repository.collaborators | vcs.github.repository.collaborators |
vcs.github.repository.commits | vcs.github.repository.commits |
vcs.github.repository.forks | vcs.github.repository.forks |
vcs.github.repository.issue_comments | vcs.github.repository.issue_comments |
vcs.github.repository.pull_request_commits | vcs.github.repository.pull_request_commits |
vcs.github.repository.pull_request | vcs.github.repository.pull_request |
vcs.github.repository.releases | vcs.github.repository.releases |
vcs.github.repository.stargazers | vcs.github.repository.stargazers |
vcs.github.repository.subscribers | vcs.github.repository.subscribers |
vcs.github.repository.events | vcs.github.repository.events |
vcs.github.api.organization.audit | vcs.github.organization.audit |
vcs.github.api.organization.sso_authorizations | vcs.github.organization.sso_authorizations |
vcs.github.api.organization.webhooks | vcs.github.organization.webhooks |
vcs.github.api.organization.dependabot | vcs.github.organization.dependabot |
vcs.github.api.repository.actions | vcs.github.repository.actions |
vcs.github.api.repository.codescan | vcs.github.repository.codescan |
vcs.github.api.repository.dependabot_alerts | vcs.github.repository.dependabot_alerts |
Table structure
This is the set displayed by these tables.
How is the data sent to Devo?
To send logs to these tables, Devo provides a collector that you can download and use to send the required events to your Devo domain. You can learn how to use it in this article GitHub collector.