Add handling to automatically group imports for per-file patches
Open
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 317
- Forks
- 76
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 5
Description
We should be able to just use imports as normal for per-file diff. It would be useful however to group all the hunks created by adding imports together into one hunk when rebuilding patches instead of having to manually move the imports around and then get annoyed when your IDE reformats them accidentally.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by tracing the per-file diff patch-rebuilding path and how import additions become separate hunks. Done means imports added through normal source usage are automatically grouped into one hunk per rebuilt patch, without manual rearrangement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100