Computer Science editorial
Open AccessOA2026
What Does It Mean and Why Should I Bother? Motivating Students to Write Better Commit Messages
A mixed-methods case study on commit-message quality and a role-based educational game (WDYM) to raise student awareness
Gergő Balogh; Péter Seres; László Tóth; Attila Szatmári; Szakács Bence; Ádám Zoltán Végh· 2026· DOI 10.48550/arXiv.2608.17993
The core problem
Software engineering instructors have long suspected that commit messages written by students often fail to serve their intended communicative role. This paper reports on a locally motivated mixed-methods case study that empirically examines this suspicion. The authors analyze commit messages from both student projects and industrial case-study projects, using a partial replication of an established commit-message quality taxonomy. The central research concern is whether communication and quality issues occur recurrently across these contexts, and if so, how a lightweight educational intervention might address them within the constraints of university coursework. The study is explicitly context-bound and does not claim general applicability beyond the studied setting. The motivating question is captured in the paper's title: students may ask, "What does it mean and why should I bother?" when confronted with commit-message guidelines. The authors aim to surface and address these communication breakdowns through a role-based educational game called What Do You Mean? (WDYM).
Innovation
The taxonomy-based analysis confirms that communication and quality issues occur recurrently in both student and industrial contexts. This substantiates the instructors' initial concern that commit messages frequently fail to serve their intended communicative role. The recurrence across both contexts suggests that the problem is not unique to students but is a broader phenomenon observable in industrial practice as well. The analysis of gameplay observations and participant surveys shows that WDYM is effective in raising awareness and fostering reflection on commit-message communication issues. However, the study provides limited evidence of immediate or sustained improvement in commit-message writing practices. In other words, the intervention succeeds in making participants think about the problem but does not conclusively demonstrate that they write better commit messages afterward. The results are presented as context-bound and do not claim general applicability beyond the studied setting.
Software engineering instructors have long suspected that commit messages written by students often fail to serve their intended communicative role. This paper reports on a locally motivated mixed-methods case study that empirically examines this suspicion. The authors analyze commit messages from both student projects and industrial case-study projects, using a partial replication of an established commit-message quality taxonomy. The central research concern is whether communication and quality issues occur recurrently across these contexts, and if so, how a lightweight educational intervention might address them within the constraints of university coursework. The study is explicitly context-bound and does not claim general applicability beyond the studied setting. The motivating question is captured in the paper's title: students may ask, "What does it mean and why should I bother?" when confronted with commit-message guidelines. The authors aim to surface and address these communication breakdowns through a role-based educational game called What Do You Mean? (WDYM).
The study employs a mixed-methods case study design. First, the authors perform a partial replication of an established commit-message quality taxonomy to analyze commit messages from student and industrial case-study projects. This taxonomy-based analysis identifies recurrent communication and quality issues. Second, motivated by the findings, the authors devise WDYM, a lightweight, role-based educational game intended to surface and address commit-message communication breakdowns within university coursework constraints. The game is evaluated through gameplay observations and participant surveys. The mixed-methods approach combines quantitative taxonomy-based classification with qualitative observational and survey data. The study is locally motivated and context-bound, meaning the intervention is designed for the specific instructional setting rather than claiming broad generalizability. The methodology can be summarized as a pipeline:
Why it matters
The findings present a nuanced picture. On one hand, the recurrent communication and quality issues in both student and industrial commit messages validate the instructors' suspicion and justify the need for an intervention. On the other hand, the limited evidence of immediate or sustained improvement suggests that raising awareness and fostering reflection may be necessary but not sufficient conditions for changing writing practices. The authors position WDYM as a useful, though imperfect, context-bound intervention for addressing a locally observed instructional problem. The study does not claim general applicability beyond the studied setting. This raises important questions for future work: What additional scaffolding or reinforcement is needed to translate awareness into sustained behavioral change? How can the constraints of university coursework be balanced against the need for repeated practice? The paper's contribution is therefore twofold: it empirically substantiates a teaching-related suspicion, and it offers a lightweight, replicable game design that can be adapted and evaluated in other contexts. The mixed-methods approach, combining taxonomy-based analysis with gameplay observations and surveys, provides a template for similar locally motivated investigations. The authors' cautious framing—acknowledging the intervention's limitations while highlighting its value—models good practice in computing education research. The study ultimately underscores that commit-message quality is a communication problem that requires both awareness and practice, and that educational interventions must be designed with realistic expectations about what they can achieve within a single course or case study.
Who should read this
CS practitioners and researchers
Opening member content…