fivetran / fivetran/dbt_github

[Feature] Add GitHub Actions Workflow Support

Abierto
#61 0 comentarios 0 reacciones 0 asignados Ver en GitHub
good first issue type:enhancement
Lenguaje dominante
Sin datos de lenguaje
Estrellas
21
Forks
24
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

### Is there an existing feature request for this?

- [x] I have searched the existing issues

### Describe the Feature

Enhance the existing data model by integrating GitHub Actions workflow data available via the Fivetran GitHub connector. Specifically, incorporate the `workflow`, `workflow_run`, and `workflow_pull_request` tables to provide visibility into CI/CD health and performance.

GitHub Actions is a critical part of modern software delivery, powering automated testing, deployments, and other CI/CD workflows. Despite this, the current data model does not expose any workflow-related metrics or insights.

By integrating workflow data into the model, teams can:
- Monitor workflow success/failure trends
- Identify performance bottlenecks in builds and deployments
- Correlate failing workflows with specific PRs, users, and branches
- Improve developer efficiency and reduce time to resolution for workflow-related issues

### How would you implement this feature?

Create staging models:
- stg_github__workflow
- stg_github__workflow_run
- stg_github__workflow_pull_request

Create an intermediate `int_github__workflow_summary` model. Aggregates and summarizes workflow execution activity at the repository and workflow level. Example Fields:
- repo_name
- workflow_name
- total_runs
- success_rate
- avg_duration_seconds
- failed_runs_last_7_days
- last_run_status

Finally a new end model `github__workflow_run_report` for enriched workflow run-level reporting. Joins workflow runs with pull requests and user metadata for context. This model would help support executive reporting on CI/CD health, provide insights into which PRs or branches introduce failing workflows, and drilldowns into long running or frequently failing workflows. Example Fields:
- repo_name
- workflow_name
- workflow_run_id
- status
- conclusion
- run_started_at
- duration_seconds
- pr_number
- pr_title
- pr_author

### Describe alternatives you've considered

_No response_

### Are you interested in contributing this feature?

- [ ] Yes.
- [ ] Yes, but I will need assistance.
- [ ] No.

### Anything else?

This feature would bring full visibility into a previously unmodeled but critical piece of the SDLC within GitHub: CI/CD workflows. It closes the loop from PR creation to automated testing and deployment, providing actionable insights for engineering and DevOps teams.

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Línea de trabajo

Comienza localizando los modelos de datos existentes del conector de GitHub y las tablas de origen workflow, workflow_run y workflow_pull_request. Revisa cómo están estructurados los modelos de staging e intermedios y, a continuación, define el resumen de workflow y el informe de workflow run solicitados en torno a los campos indicados. El trabajo estará terminado cuando los tres modelos de staging, int_github__workflow_summary y github__workflow_run_report proporcionen las métricas de CI/CD y el contexto de pull request indicados.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
github-actions
Área
analytics, ci-cd, data-engineering
Tipo de issue
Nueva funcionalidad
Dificultad
5/5
Tiempo estimado
Más de una semana
Estado de actividad
Estancado
Claridad
Bastante claro
Aptitud para principiantes
35/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.