-
Notifications
You must be signed in to change notification settings - Fork 0
faq
Git Recap is a developer productivity tool that aggregates and summarizes your Git activity across multiple platforms (GitHub, GitLab, Azure DevOps) into a concise, actionable format. It fetches commit messages, pull requests, and issues, then consolidates them into a chronological summary.
Currently supported providers:
- GitHub (via PyGitHub)
- GitLab (via python-gitlab)
- Azure DevOps (via azure-devops Python API)
Yes! You can use the GitHub App version from the Marketplace, or run your own instance using the open-source code.
You have several options:
- GitHub App: Install from Marketplace (recommended)
- Personal Access Token (PAT): Generate a token with proper permissions
- OAuth: Coming soon!
The app requires:
- Read access to repositories
- Read access to pull requests
- Read access to issues
-
GitHub:
- Go to Settings > Developer settings > Personal access tokens
- Select
reposcope
-
GitLab:
- User Settings > Access Tokens
- Select
read_repositoryscope
-
Azure DevOps:
- User settings > Personal access tokens
- Select "Code (read)" scope
Use the --start-date and --end-date parameters in ISO format (YYYY-MM-DD or YYYY-MM-DDTHH:MM:SS). Dates without timezone info are automatically converted to UTC.
Yes! Use the --authors parameter followed by the usernames you want to include. By default, it uses the authenticated user.
The tool outputs:
- JSON format with all raw events
- A plain text summary grouped by day (ideal for LLM context)
This typically means:
- Your session expired (sessions last 5 minutes)
- The WebSocket connection was interrupted Solution: Try re-authenticating.
The API has rate limiting enabled to prevent abuse. Wait a few seconds and try again.
- Check your internet connection
- Ensure your firewall isn't blocking WebSocket connections (port 443)
- Try refreshing the page
- Check browser console for errors
Possible causes:
- The app hasn't been installed on the target organization
- PAT doesn't have proper repo permissions
- Repository is archived Solutions:
- For GitHub: Check Marketplace installation status
- Regenerate PAT with correct permissions
- Ensure repos are active
Yes! The architecture is modular. Create a new class inheriting from BaseFetcher in the providers directory.
See our Contributing Guide for setup instructions and coding standards.
Please open an issue on our GitHub repository with:
- Steps to reproduce
- Expected behavior
- Actual behavior
- Screenshots if applicable
Fetching history for large repos takes time. Consider:
- Narrowing the date range
- Using more specific filters
- Running during off-peak hours
Currently no, but caching is planned for a future release.