This repository serves as a system for using GitHub Issues as a micro-notes platform, similar to a microblog or services like Flomo. It periodically processes these issues and exports their content into a JSON file, making them accessible for external applications or services.
This repository automatically processes GitHub Issues labeled "Public" and generates a public/issues.json file. This allows you to use GitHub Issues as a lightweight CMS for micro-notes or blog posts, with the content made available in a structured JSON format.
See it in action: https://me.deeptoai.com/musings
This system powers a fully functional microblogging platform that:
- 📝 Displays GitHub Issues as elegant blog posts
- ✍️ Allows publishing new musings directly from the web interface
- 🏷️ Supports tag-based filtering and organization
- 📱 Features responsive design with modern UI
- 🔄 Auto-syncs content via GitHub Actions
Technical Implementation: For detailed setup instructions and integration examples, see Musings System Documentation
The generated JSON is available at:
https://raw.githubusercontent.com/foreveryh/git-thoughts/main/public/issues.json
// Fetch musings data
const response = await fetch(
'https://raw.githubusercontent.com/foreveryh/git-thoughts/main/public/issues.json'
);
const musings = await response.json();
// Each musing object contains:
// { id, number, title, body, url, created_at, updated_at, tags }For complete Next.js integration with publishing capabilities, see the technical documentation.
Core Components:
- ⚡ Real-time Sync: Auto-triggers when Issues with "Public" label are created/edited
- 🔄 GitHub Actions Workflow: Automatically syncs Issues → JSON
- 📝 Node.js Script: Fetches and processes public issues via GitHub API
- 🔒 External Issue Filter: Blocks non-owner submissions while preserving blog posts
- 📊 Structured Export: Clean JSON format optimized for frontend consumption
Key Features:
- ⚡ Real-time Updates: New/edited Issues trigger instant JSON sync
- ✅ Smart Filtering: Only processes Issues with "Public" label
- ✅ Optimized Triggers: Avoids unnecessary runs for better performance
- ✅ Tag Preservation: Maintains all labels except "Public"
- ✅ Auto-generated Metadata: Titles, timestamps, and structured data
- ✅ Conflict-free Operation: Safe for use with external repositories
Sync Triggers:
- 🎯 Content Changes: When Public Issues are created or edited (not just labeled)
- ⏰ Scheduled: Daily at 2 AM UTC for reliability
- 🔄 Manual: On-demand via GitHub Actions interface
Issues with "Public" label automatically trigger JSON updates on content changes:
- ✅ Creating new Issues
- ✅ Editing existing content
- ❌ Adding/removing labels alone (optimized to avoid unnecessary runs)
Daily sync at 2 AM UTC ensures consistency
For immediate updates:
- Go to Actions tab → "Sync Public Issues to issues.json"
- Click "Run workflow" button
- Updated
issues.jsonwill be committed automatically
┌─────────────────┐ ┌──────────────────┐ ┌─────────────────┐
│ Blog/App │◄──►│ GitHub API │◄──►│ GitHub Issues │
│ │ │ │ │ │
│ - Fetch JSON │ │ - Read issues │ │ - Content store │
│ - Display posts │ │ - Create issues │ │ - Public label │
│ - Publish UI │ │ - Auto sync │ │ - Tag system │
└─────────────────┘ └──────────────────┘ └─────────────────┘
│ │ │
▼ ▼ ▼
┌─────────────────┐ ┌──────────────────┐ ┌─────────────────┐
│ Raw JSON URL │ │ GitHub Actions │ │ External Filter │
│ │ │ │ │ │
│ - Public access │ │ - Scheduled sync │ │ - Block others │
│ - ISR friendly │ │ - Auto commit │ │ - Preserve blog │
│ - No auth req'd │ │ - Error handling │ │ - Auto close │
└─────────────────┘ └──────────────────┘ └─────────────────┘