In our article “What really changes when developers intend to improve their source code: a commit-level study of static metric value and static analysis warning changes” recently published in Empirical Software Engineering, we investigate changes in static source code metrics and static analysis warnings associated with software quality in commits where developers intend to improve the quality. Two researchers manually classify a sample of commit messages to extract the developer intention. We then use this sample to fine-tune a pre-trained language model and use the final model to classify the rest of the data. Using this data, we can show that most of the static source code metric values associated with quality move in the expected direction and static analysis warnings are reduced in commits where the developers intend to improve quality. However, when quality is increased via fixing bugs, we see that complexity is increasing in comparison to all other changes to the codebase. Our investigation also shows that bug fixes are applied to large and complex files, while improvements are mostly applied to files which are already small and less complex. Together these two results show that bug fixes increase complexity but that it is not necessarily corrected later as those improvements are mainly applied to already less complex files.