Open
Description
Can we correlate git
change data with migration data?
git
change 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