Module insights map

The gist

Once you have mapped your codebase into modules with the module mapping tool Codigy will generate maps for each module. 

This map gives a clear picture of how the module is changed. This map is based on longer periods (i.e. 30 days) so frequently repeated patterns become more prominent.

This is an excellent way to identify: if the module is:

• If modules in changed with other modules;

• If someone besides the assigned owner is changing this module;

Addressing these targets, will increase your team autonomy and reduce codebase coupling.

Module info & metrics

Assigned owner - team that is expected to maintain the module and review all PRs. Usually it is a team with the most hands-on experience, Confidence metric can help you check if that is the case.

Confidence - level of hands-on experience each team has with the files in this module. In case you wan't to re-assign the module to another team - you do this through this interface.

Mapping rules timestamp - date and author of the mapping rules.

Last change - last recorded feature that affected the module.

Module map

Module map shows all the files that were mapped into a module. Map can contain files from single or multiple repositories.

Map highlight filters

Map is interactive. You can highlight specific data on the map:

1. Activity - highlights files that were changed during selected period. Itensity of the color correlates with frequency of changes. Green color indicates changes made by the assigned owner. Red highlights changes made by other teams.

2. Changes by other teams - highlights only the files that were changed by other teams in the selected period. Intensity of the color indicates frequency of such events. Addressing these hotspots will help increase your team autonomy.

3. Mapped in multiple modules - it is possible for file to be mapped in multiple modules simultaneously. However, this is not optimal as it increases coupling and complexity of your codebae. This filter will allow you to highlight and address these targets.

File & folder actions

All elements on the map are interactive. By hovering over files and folders you can find CODEOWNERS and Confidence information for each element. 

Ignore - we recommend to add all autogenerated and non-binary files to ignore list. You can do this by hover over an element on the map and accessing the action menu.

Re-assign - in case you want to move file or folder to another module, you can do this from the action menu.

Deep File Context

To start investigting a hotspot, you can click on the file and a list of all the features that affected the file along with a list of relevant PRs.