How to count your merged GitHub pull requests by month
Use Pull Tally to browse your merged pull requests month by month, filter by owner, and export the results. For an occasional lookup, GitHub search can give you a total and the matching PRs. This guide shows both approaches and explains what each count includes.
By Pull Tally · Updated
Browse your monthly history with Pull Tally
When preparing a monthly recap, select a month to see your total, daily graph, and matching PRs. Choose an owner to narrow the view, move between months without editing search dates, and follow the original PR links to revisit the work. To use the results in a spreadsheet, export the selected month as CSV.
Try a concrete example: the fictional August 2026 history contains five merged PRs across three owners. Select acme-labs to see its three PRs, then move to July to see how the total, graph, and list change together.
Explore Pull Tally with fictional example data. You can try the month and owner controls without connecting GitHub. Access to your own history and CSV export is currently through the invite-only beta.
Look up a month with GitHub search
Sign in to GitHub and paste this into global search. This example selects August 2026; change both dates for another month.
is:pr is:merged author:@me merged:2026-08-01..2026-08-31Read the result total, then browse the matching PRs. The filters select pull requests, merged state, your author filter, and a merge-date range.
Use author:YOUR-USERNAME instead of author:@me when specifying a username. Keep the author filter: removing it changes whose work is counted.
Search across repositories, or narrow the scope
Global search can span repositories you can access. Append org:YOUR-ORG for an organization, user:YOUR-USERNAME for a personal owner's repositories, or repo:OWNER/REPOSITORY for one repository. Replace the uppercase placeholders.
Private results require the appropriate GitHub access. An organization filter identifies the repository owner; it does not replace the author filter.
Count by merge date, not creation date
Consider this fictional history for one author. The August search counts one PR: the change merged on August 4, even though it was opened in July.
| Pull request | Opened | Outcome | Counted? |
|---|---|---|---|
| Fix date filtering | July 29 | Merged August 4 | Yes |
| Add export labels | August 30 | Merged September 2 | No |
| Try a new chart | August 12 | Closed without merging | No |
A useful work recap starts with the matching PRs. Read the descriptions and follow the changes before drawing conclusions from the total.
What can change the total?
The author and the person who merged are different roles
This search follows the author filter. It is not a record of who pressed the Merge button. GitHub also includes PRs created by Copilot on your behalf in author searches, so the result is not necessarily a count of PRs you created manually.
Month boundaries need a consistent time zone
For a merge close to midnight, check its timestamp before comparing two reports. Pull Tally groups months in your browser's time zone; a date-only GitHub search is not guaranteed to match that exact window. GitHub's date-search reference explains dates and UTC offsets.
Access and filters define what you can see
Check the selected author, owner, dates, and current repository access when an expected PR is missing. In Pull Tally, private repositories must also be connected through its GitHub App. Selecting only some repositories gives partial private coverage. Read the GitHub access details.
Pull Tally's history uses your current access rather than a permanent archive. If a selection cannot be returned completely, it shows an explanation instead of a tally.
A PR count is a way to find and revisit work. It does not measure the difficulty, quality, or impact of that work.
Save your monthly results as CSV
To work with your results in a spreadsheet, select a month and an optional owner filter in Pull Tally, then choose Export month (CSV). The export covers the full selected month within your available repository coverage, including results beyond the current page.
The file includes each PR's repository, number, title, merge time, and GitHub link, plus the selected month, time zone, owner filter, repository coverage, and when the data was fetched.
Use it to sort your contributions, prepare a monthly report, or keep a snapshot of the results.