-
-
Notifications
You must be signed in to change notification settings - Fork 7
Sync Settings
Configure how and when the plugin synchronizes with GitHub.
Click the GitHub sync icon in the left ribbon to trigger a full sync.
Use the command palette: Sync GitHub issues & pull requests
When enabled, automatically syncs all repositories and projects when Obsidian starts.
Default: Enabled
Enable periodic automatic synchronization while Obsidian is running.
How often to sync in the background.
- Minimum: 5 minutes
- Recommended: 15-30 minutes
Higher intervals reduce API usage and improve performance.
Automatically delete local files for items that have been closed for longer than the specified number of days.
- Minimum: 1 day
- Default: 30 days
- Tip: Set higher if you want to keep closed items longer
Files are deleted when:
- The issue/PR is closed longer than the cleanup period
- The item no longer matches your filters (labels, assignees)
- The item was deleted on GitHub
- The repository/project was removed from tracking
Each file has an allowDelete frontmatter property:
---
allowDelete: true
---Set to false to prevent automatic deletion of a specific file.
Control how many notifications you see during sync:
| Level | Shows |
|---|---|
| Minimal | Only errors and important messages |
| Normal | Start/end of sync, errors |
| Extensive | Detailed progress for each repository |
| Debug | All debug messages (for troubleshooting) |
Each sync operation:
- Fetches issues matching your filters
- Fetches pull requests matching your filters
- Creates new files for new items
- Updates existing files (based on update mode)
- Removes files for deleted/filtered items
- Cleans up old closed items
Files are only updated when:
- The
updated_attimestamp on GitHub is newer - The issue/PR state changed (open ↔ closed)
This prevents unnecessary file modifications.
Content inside Persist-Blocks is preserved during updates, even when using "Update" mode.
The plugin respects GitHub API rate limits:
- Authenticated: 5,000 requests/hour
- Sync operations are optimized to minimize API calls
- Background sync helps spread requests over time
- Start with manual sync to verify your settings work correctly
- Use background sync for hands-free updates
- Set reasonable intervals (15+ minutes) to avoid hitting rate limits
- Use filters to reduce the number of items synced
- Check notification level if sync seems slow - Debug mode shows detailed progress