...
Most Frequently Modified Files shows top 20 files having the biggest counter of modifications per each connected GIT repository - over selected time frame (30 days, 90 days, since project start). This works based on information from GIT about commits history, having paths of files associated with each commit.
...
Most Frequently Modified Files helps to find out the most fragile points in the code base / architecture by showing a modification frequency for files in a project code base. Once appropriate file (or a group of files) is identified, it is usually a risk of S.O.L.I.D.design principles violation in that area - and this requires, at least, a thorough code review or even a refactoring in order to keep the maintainability of the code on a controllable level.
| Tip | ||
|---|---|---|
A deeper explanation why following S.O.L.I.D. principles in software development is important - and a practical exercise of applying S.O.L.I.D. principles - is recommended to watch at https://www.youtube.com/watch?v=8ZJ8BVlDIQ4: | https://www.youtube.com/watch?v=8ZJ8BVlDIQ4 |
How metric works
Chart overview
Chart shows Most Frequently Modified Files in a number of changes (Axis Y) by file name (Axis Y). The chart can be viewed for the last 30/90 days of for the whole project duration in GIT.
Next to the chart name there is a link to navigate to the GIT repository ('arrow' icon) for further details.
...
Calculation
Total value for a file is a number of changes made in this file during a considered period. Then the total values for all files are placed in descending order and first 20 file names are shown in the chart.
If 'Files to exclude' is is specified in in GIT configuration the the metric values might change.
RAG thresholds: n/a.
Data Source
Data for the metric can be collected from GIT.
| Insert excerpt | ||||||||
|---|---|---|---|---|---|---|---|---|
| Include Page | EPMDMO-ga-toplevel-ASSURE | |||||||
| EPMDMO-ga-toplevel-ASSURE | ||||||||
| Include Page | ||||||||
|