GitHub
Import activities from a GitHub repository
What is it?
GitHub as a Source lets you store your fitness activities as Markdown files inside a Git repository. Each activity file uses YAML frontmatter for structured metadata (title, type, date) and can optionally reference a .fit file for full telemetry data.
How it works
When you push a commit containing new or modified .md files to your configured folder, a GitHub webhook fires and FitGlue automatically picks up the changes. FitGlue parses the YAML frontmatter — title, activity type, distance, and more — and creates a standardised activity that flows through your pipeline.
If the frontmatter contains a fit_file field pointing to a .fit binary in the same repository, FitGlue downloads the file and attaches the full telemetry (heart rate, GPS, cadence, power) so that boosters like Heart Rate Zones and Muscle Heatmap can process the data.
File Format
Activity files follow a simple convention:
---
title: "Morning Run"
type: running
date: 2026-02-08
distance_km: 5.2
fit_file: ./morning-run.fit
---
Optional free-text notes here.
Safety & Privacy
- FitGlue only reads files inside your configured folder — nothing else in the repo is accessed.
- Webhook payloads are verified via HMAC-SHA256 to prevent spoofing.
- Commits authored by "FitGlue Bot" are automatically ignored to prevent infinite loops when GitHub is also a destination.
- Your OAuth token is stored encrypted and is only used to fetch file contents.
Features
- ✅ Version-controlled activity history
- ✅ Full FIT file telemetry support
- ✅ YAML frontmatter for structured metadata
- ✅ HMAC-SHA256 webhook verification
- ✅ Automatic loop prevention
- ✅ Works with any public or private repository
Required Connection
This Booster requires the following Connection: