feat(gitter): New endpoint for commit history and patch extraction - #6009
Open
Ly-Joey wants to merge 2 commits into
Open
feat(gitter): New endpoint for commit history and patch extraction#6009Ly-Joey wants to merge 2 commits into
Ly-Joey wants to merge 2 commits into
Conversation
Ly-Joey
changed the title
- Truncate diff patch if too big (exceeds 5MB) - Optional path filtering if we want to exclude e.g doc paths - Optimize commit log parsing
Ly-Joey
force-pushed
the
feat-gitter-commits
branch
from
September 11, 2026 05:58
8627e0d to
a4754b0
Compare
Ly-Joey
marked this pull request as ready for review
September 11, 2026 06:08
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
/commit-diffsendpoint to return structured commit data (SHA, timestamp, message, diff patches, and modified files) relative to a target branch and last sync point.The last-sync reference can be a commit SHA or timestamp.
When both are provided, the commit hash is prioritized, with the timestamp acting as a fallback if the hash is invalid (e.g., from a git commit --amend or rebase).