Add diff prioritization and truncation with notices
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
Research direction
Start by tracing the existing MAX_TOKENS handling that excludes oversized files, then read the linked context in #183. Identify where diffs are ordered and rendered. Done means code, documentation, and test files receive the stated priority, oversized diffs are partially retained, and truncated files include the specified notice.
Written by the indexing model from the issue text.
Description
When total diff exceeds token limits, we should prioritize core logic files over documentation or tests, and truncate individual file diffs with a notice like:
... [diff truncated for length]
Currently, files exceeding the MAX_TOKENS limit are simply excluded entirely. We need a more nuanced approach that:
- Prioritizes certain file types (code > docs > tests)
- Truncates large diffs instead of excluding them entirely
- Appends truncation notices
Originally identified in #183 - Smart Token Budgeting & Large Diff Truncation.
- Dominant language
- Go
- Stars
- 0
- Forks
- 0
- Avg merge
- 13h 29m
- Merged PRs (30d)
- 11
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from rm-hull/git-commit-summary
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
rm-hull/git-commit-summary#189 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
rm-hull/git-commit-summary#185 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 45/100
rm-hull/git-commit-summary#184 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 45/100
rm-hull/git-commit-summary#183 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
rm-hull/git-commit-summary#106 ·
Maintainers usually reply within 1 day
All issues in rm-hull/git-commit-summary
Similar issues
-
area/docs kind/documentation priority/backlog triage/accepted
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
lexfrei/cloudflare-tunnel-gateway-controller#943 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
keyxmakerx/Chronicle#967 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
[E2E Scenario Tests] HTTP logs capture export requests from test framework, polluting golden filesOpen
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
GoogleCloudPlatform/k8s-config-connector#13675 ·
Maintainers usually reply within 1 day