Git Email Extractor

What does Git Email Extractor do?

Git Email Extractor takes a list of git repository URLs, performs a shallow clone of each one, and scans the commit history for author and committer emails (including addresses mentioned in commit message trailers like Co-authored-by). Useful for mapping out contributors to open source projects, auditing internal repos, or lead-gen research on maintainers of a codebase.

Why use Git Email Extractor?

• Quickly identify all contributors to a repository without cloning and grepping manually.
• Run against many repositories in one go via the Apify platform's API, scheduler, and integrations.
• Get structured, downloadable results (JSON/CSV/Excel) instead of parsing git log output by hand.

How to use Git Email Extractor

1. Open the Actor's Input tab.
2. Add one or more git repository URLs (HTTPS clone URLs, e.g. https://github.com/user/repo.git).
3. Optionally adjust the shallow clone depth (how many recent commits to scan per repo).
4. Run the Actor and check the Dataset tab for results.

Input

Field	Type	Description
repoUrls	array of strings	Git repository URLs to clone and scan.
cloneDepth	integer	Number of most recent commits to fetch per repo (default 100). Only commits within this depth are scanned.

Output

Example dataset items — one flat row per name/email pair found:

[
  { "repoUrl": "https://github.com/apify/apify-sdk-python.git", "name": "Jane Doe", "email": "jane@example.com" },
  { "repoUrl": "https://github.com/apify/apify-sdk-python.git", "name": "John Smith", "email": "john@example.com" }
]

You can download the dataset in various formats such as JSON, HTML, CSV, or Excel.

Data table

Field	Description
repoUrl	The repository URL the row was found in.
name	Display name associated with the email in the commit history.
email	The extracted email address.

Pricing / Cost estimation

Cost scales with the number of repos and the clone depth you set — cloning is the dominant cost, since email extraction itself is cheap local text processing. Use a smaller cloneDepth if you only need recent contributors.

Tips

• Only public (or otherwise accessible) HTTPS repo URLs are supported — private repos requiring auth aren't handled.
• noreply addresses (e.g. GitHub's privacy emails) are filtered out automatically.
• Increase cloneDepth if a repo has many contributors further back in history you want to catch.

FAQ, disclaimers, and support

Only scrape repositories you have the right to access and process. Respect the license and any usage terms of the target repositories. Found a bug or have a feature request? Open an issue on the Actor's Issues tab.