Feature Request: Incorporate Git Change Data?
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 129
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Can we correlate git change data with migration data?
gitchange data tells you the places in the code (e.g. files) where folks are making changes- so from that you get a heap map of "which files are getting the most changes over the last X, e.g. year"
- you take that data, then you run your invert scripts and so for every file (or module) you know:
- how many things need to be fixed / improved in it
- how many changes have been happening
This is all super important because if you have 100 files that need to be migrated, they're not all equal.
A file that's getting a lot of other changes is a hot file. The tech debt is constantly in people's way. It's super costly
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
The issue names no files, tests, or entry points, so first map the existing migration data and invert scripts before deciding where Git history and file-level change counts belong. Define the supported time window, file or module aggregation, and an acceptance check showing migration work alongside change frequency.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, kotlin
- Domain
- analytics, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100