Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Connector Improvement: Github: Add Workflow run logs

Answered
Filip Rodik User

Add execution log data for Github Workflows to the Github Connector schema.

Please sign in to leave a comment.

Comments

4 comments

Date Votes
  • Official comment
    Erin Fivetranner

    Hi Filip - Thanks for submitting this feature request. We don't currently have this planned, but i will put it on the backlog and will continue to monitor for future development. 

    Do you mind sharing a bit about your use case for execution log data in GitHub? I'm not super familiar with this endpoint and I would love to better understand how this data will serve your analysis of a specific area. 

    Best, 

    Erin

  • Filip Rodik User

    Hi Erin,

    We are using Github Workflows for CI/CD as well as regular ETL. Some custom logging is implemented for monitoring execution (duration) of critical processes. Instead of relying on custom logs (and/or manual pulls from Github API) it would be nice to have this provided by your connector. The github dbt package could also be extended with models derived from the dataset.

    Regards,

    Filip

  • Arjel Miras User
    We’re interested in the Github Workflows/Actions dataset as it records the runtime and statuses of build steps relevant in Continuous Integration and deployments to production. We already report these build-related metrics for the CI/CD platforms Xero currently uses. Xero is looking to adopt Github Workflows/Actions as a CI/CD platform. In order to provide the same level of metrics we need access to the underlying data. Hence the request.Currently our datastack does not use Fivetran to ingest this Github and CI/CD platform data into the data lake. We’re in the early days of Fivetran adoption as an org. If the Fivetran Github Connector can bring in this Workflow/Action data it greatly increases the value prop of Fivetran as we can replace the custom integrations.
  • Maximilian Eber User

    We have the exact same use case: Would be great to pull those out of the API and include them in the DBT package.