GitHub Pre-built templates
Renta pipeline templates create several related GitHub pipelines in one action. You pick the template and the repositories, and Renta creates one pipeline per report type in the template.
Overview
Each template bundles the report types around one task.
| Template | Pipelines it creates |
|---|---|
| GitHub — all objects | One pipeline per report type available for the source. |
| GitHub — repository basics | Repositories, Branches, Tags, Commits, Releases. |
| GitHub — issues & pull requests | Issues, Issue Comments, Issue Events, Issue Milestones, Issue Labels, Pull Requests, Pull Request Commits, Reviews, Review Comments, Pull Request Stats. |
| GitHub — CI/CD | Workflows, Workflow Runs, Workflow Jobs, Deployments, Commit Check Runs. |
| GitHub — organization | Repositories, Teams, Team Members, Collaborators, Assignees. |
Default settings
Every pipeline a template creates starts with the same values.
- Fields.
All fields of the report type are selected. The field list of each type is visible in the Parameters picker of a custom report. - Table name.
A fixed name in the github_{report_type} format: the Commits pipeline writes to thegithub_commitstable. - Pipeline name.
The template name plus the report type, for exampleGitHub — CI/CD — workflows. - Overwrite period.
Last 1 day.
The repositories, the date range, and the schedule you set on the form apply to every pipeline of the template. The pipelines sync the same way as custom reports of the same report type, as described in the Sync strategy section.
After the pipelines are created, you can open each one in the pipeline settings and change the values.
Data relationships
The tables join by identifier columns.
- Jobs to runs.
Joingithub_workflow_jobswithgithub_workflow_runsby therun_idandidcolumns. - Runs to workflows.
Joingithub_workflow_runswithgithub_workflowsby theworkflow_idandidcolumns. - Review comments to reviews.
Joingithub_review_commentswithgithub_reviewsby thepull_request_review_idandidcolumns. - Check runs to commits.
Joingithub_commit_check_runswithgithub_commitsby thehead_shaandshacolumns. - Comments to issues and pull requests.
github_issue_commentscarries theissue_urlcolumn andgithub_reviewscarriespull_request_url. Join them to theurlcolumn ofgithub_issuesandgithub_pull_requests.
The repository behind a row is visible in its URL columns, such as Repository URL or HTML URL. Rely on them to separate data when the pipeline reads several repositories.
Creating with template
Follow these steps on the settings screen of the GitHub pipeline.

- Select Pre-built templates as the integration type.
- Select the template in the Templates dropdown.
- Choose the Repositories.
Set the date range and the schedule as usual. These settings apply to all pipelines of the template.
After you click Create pipeline, the pipelines appear in the Pipelines section under the ETL tab.
The GitHub — all objects template is the heaviest option. On an account with hundreds of repositories, the first run of the resulting pipelines can exhaust the hourly GitHub API budget, and the remaining pipelines finish on later runs.
Template or custom report
A template is a quick start with every field selected. A custom report gives you full control over the configuration.
| Feature | Template | Custom report |
|---|---|---|
| Setup | One action creates a pipeline per report type | Each pipeline is configured separately |
| Field selection | All fields of the report type | Your own selection |
| Schedule | One schedule for all pipelines of the template | Configured per pipeline |
| Use case | A full copy of GitHub objects in the warehouse | Custom data requirements |
Ready to get started?
Build your data pipeline today or get a personalized demo. Start free!
Need help?
Get expert support to ensure your project succeeds. We're here to help!
Feature requests?
Help shape our product! Share your ideas for new features and integrations.