GitHub
Commit enriched activities to a GitHub repository
What is it?
GitHub as a Destination commits your enriched activities as Markdown files to a Git repository. Each activity becomes a versioned document containing your title, description, booster output, and metadata — all stored in your own repo under your full control.
How it works
After your activity passes through the FitGlue pipeline and all boosters have run, the enriched result is committed to your chosen repository. The file is placed inside your configured folder, organised by year, month, and date (e.g. workouts/2026/02/2026-02-08-morning-run/activity.md).
Commits are authored by "FitGlue Bot" so they are clearly distinguishable from your own work. If GitHub is also configured as a source, this author name is used for automatic loop prevention — FitGlue ignores its own commits.
File Structure
Each committed Markdown file includes:
- YAML frontmatter — title, activity type, date, source, pipeline ID, applied enrichments, and tags
- Heading and description — the full enriched description with all booster sections
<!-- fitglue:end -->marker — anything you write below this line is preserved across updates
Safety & Privacy
- Only the configured folder is written to — FitGlue never modifies other files.
- Updates preserve any content you add below the
fitglue:endmarker. - All commits use the FitGlue Bot identity for traceability.
- Your OAuth token is stored encrypted and scoped to the
repopermission.
Features
- ✅ Full Git history for every activity update
- ✅ Organised by year/month/date folder structure
- ✅ User content preserved below fitglue:end marker
- ✅ FitGlue Bot commits for clear attribution
- ✅ Automatic loop prevention with source
- ✅ Works with public and private repositories
Required Connection
This Booster requires the following Connection: