Deciphering WONTFIX: A Mixed-Method Study on Why GitHub Issues Get Rejected
J. Alexander Curtis, Sharadha Kasiviswanathan, Nasir Eisty
TL;DR
This study investigates the wontfix label on GitHub across 3,132 popular repositories using a mixed-methods approach that combines quantitative prevalence analysis with qualitative grounded theory. It finds that about 30% of top projects apply wontfix to issues or PRs, with a higher incidence on issues, and identifies eight themes behind labeling decisions split between submitter- and maintainer-controlled factors. The results offer actionable guidance for submitters to improve submission quality, for maintainers to manage expectations and transparency, and for tooling to enhance inclusivity and workflow efficiency. The work highlights potential risks to community morale and transparency, while proposing strategies such as better documentation and translation support to mitigate negative effects and promote healthier open-source collaboration.
Abstract
Context: The ``wontfix'' label is a widely used yet narrowly understood tool in GitHub repositories, indicating that an issue will not be pursued further. Despite its prevalence, the impact of this label on project management and community dynamics within open-source software development is not clearly defined. Objective: This study examines the prevalence and reasons behind issues being labeled as wontfix across various open-source repositories on GitHub. Method: Employing a mixed-method approach, we analyze both quantitative data to assess the prevalence of the wontfix label and qualitative data to explore the reasoning that it was used. Data were collected from 3,132 of GitHub's most-popular repositories. Later, we employ open coding and thematic analysis to categorize the reasons behind wontfix labels, providing a structured understanding of the issue management landscape. Results: Our findings show that about 30% of projects on GitHub apply the wontfix label to some issues. These issues most often occur on user-submitted issues for bug reports and feature requests. The study identified eight common themes behind labeling issues as wontfix, ranging from user-specific control factors to maintainer-specific decisions. Conclusions: The wontfix label is a critical tool for managing resources and guiding contributor efforts in GitHub projects. However, it can also discourage community involvement and obscure the transparency of project management. Understanding these reasons aids project managers in making informed decisions and fostering efficient collaboration within open-source communities.