# Feature Request: Git Integration for Version Control of TagoIO Development Assets

**URL:** <https://community.tago.io/t/feature-request-git-integration-for-version-control-of-tagoio-development-assets/1920>\
**Category:** Feature Request\
**Created:** [September 15, 2026, 5:06pm UTC](https://community.tago.io/t/feature-request-git-integration-for-version-control-of-tagoio-development-assets/1920 "2026-09-15T17:06:31Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![alexd](https://avatars.discourse-cdn.com/v4/letter/a/96bed5/32.png) [@alexd](https://community.tago.io/u/alexd)\
**Post date:** [September 15, 2026, 5:06pm UTC](https://community.tago.io/t/feature-request-git-integration-for-version-control-of-tagoio-development-assets/1920/1 "2026-09-15T17:06:31Z")

</div>

**Summary**  
TagoIO analyses already have internal version control, but this history is siloed inside the platform. Add the ability to sync that version history with an external Git repository (GitHub, GitLab, Bitbucket, or self-hosted), and extend version control/Git sync to payload parsers, custom widgets, and other custom code that currently has none.

**Problem**

1. **Analyses** : version history exists, but only inside TagoIO’s own UI. There’s no way to push that history to a repo our team actually works out of, review via pull requests, or diff against our own branching workflow. It’s a dead end, useful for rollback inside TagoIO, but disconnected from our real development process.
2. **Payload parsers, custom widgets, and other custom code** : no version control at all. Any edit overwrites the previous version with zero history or rollback.

This means our team has to manually copy code out of TagoIO into our own repo to track it properly, and that copy silently goes stale whenever someone edits directly in the TagoIO editor.

**Proposed Solution**

- Let a TagoIO account/application be linked to a Git repo (OAuth or SSH/deploy key).
- Push each saved version of an analysis (i.e., what already triggers TagoIO’s internal versioning) as a commit to the linked repo, preserving timestamps/authorship where possible.
- Support pull too: deploying a specific commit/branch/tag from the repo into TagoIO as the active analysis version.
- Extend actual version control (not just Git sync) to payload parsers and custom widget code, which currently have none then sync those the same way.
- Optional: webhook/CI trigger so a merge to a chosen branch auto-deploys to TagoIO.

**Use Cases**

- Code review via pull requests before an analysis version goes live.
- One real source of truth instead of TagoIO’s internal history and our repo drifting apart.
- Rollback and diffing using our own tools instead of TagoIO’s separate versioning UI.
- Version control (and eventually Git sync) for parsers/widgets, which currently have no safety net at all.

**Benefits to TagoIO**

- Closes a real gap: version history exists but isn’t usable in normal dev workflows.
- Removes a recurring manual-sync task that’s a common source of drift/errors for teams building on TagoIO.
- Extends parity across all custom-code surfaces instead of analyses being the only one with any history.

---

<div class="post-metadata">

**Author:** ![carolina.hidalgo](https://yyz2.discourse-cdn.com/flex034/user_avatar/community.tago.io/carolina.hidalgo/32/1602_2.png) [@carolina.hidalgo](https://community.tago.io/u/carolina.hidalgo)\
**Post date:** [September 18, 2026, 12:24pm UTC](https://community.tago.io/t/feature-request-git-integration-for-version-control-of-tagoio-development-assets/1920/2 "2026-09-18T12:24:47Z")

</div>

Hi @alexd

Thank you so much for this suggestion!

We’ve already passed it along to the team responsible for reviewing it, and who knows, we might implement it down the line.

If that happens, I’ll keep you posted.

Thanks again, feedback like this always helps us improve!