Should I Stale or Should I Close? An Analysis of a Bot That Closes Abandoned Issues and Pull Requests

Wessel, Mairieli; Steinmacher, Igor; Wiese, Igor; Gerosa, Marco Aurélio

doi:10.1109/botse.2019.00018

Cited by 29 publications

(21 citation statements)

References 19 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Finally, various projects have proposed DevBots for a wide range of software engineering tasks. Examples include agile team management [1,18], program repair [29,30], software visualization [4], source code refactoring [33], or pull request management [32]. Our work is orthogonal to these studies, as we are not proposing any concrete new type of DevBot.…”

Section: Related Workmentioning

confidence: 99%

An empirical study of bots in software development: characteristics and challenges from a practitioner’s perspective

Erlenhov

Neto

Leitner

2020

Proceedings of the 28th ACM Joint Meeting on European Software Engineering Conference and Symposium on the Foundations of Softw

View full text Add to dashboard Cite

Software engineering bots ś automated tools that handle tedious tasks ś are increasingly used by industrial and open source projects to improve developer productivity. Current research in this area is held back by a lack of consensus of what software engineering bots (DevBots) actually are, what characteristics distinguish them from other tools, and what benefits and challenges are associated with DevBot usage. In this paper we report on a mixed-method empirical study of DevBot usage in industrial practice. We report on findings from interviewing 21 and surveying a total of 111 developers. We identify three different personas among DevBot users (focusing on autonomy, chat interfaces, and łsmartnessž), each with different definitions of what a DevBot is, why developers use them, and what they struggle with. We conclude that future DevBot research should situate their work within our framework, to clearly identify what type of bot the work targets, and what advantages practitioners can expect. Further, we find that there currently is a lack of generalpurpose łsmartž bots that go beyond simple automation tools or chat interfaces. This is problematic, as we have seen that such bots, if available, can have a transformative effect on the projects that use them. CCS CONCEPTS • Software and its engineering → Software notations and tools.

show abstract

Section: Related Workmentioning

confidence: 99%

An empirical study of bots in software development: characteristics and challenges from a practitioner’s perspective

Erlenhov

Neto

Leitner

2020

Proceedings of the 28th ACM Joint Meeting on European Software Engineering Conference and Symposium on the Foundations of Softw

View full text Add to dashboard Cite

show abstract

“…After the CSM is applied to the main stem, it is iteratively applied to the other stems, starting with the one with the most recent commit. We determine the processing order to preserve the topology of critical stems first, following the valuation criteria in a prior work [71].…”

Section: Context-preserving Squash Merge (Csm)mentioning

confidence: 99%

Githru: Visual Analytics for Understanding Software Development History Through Git Metadata Analysis

Jeon

Kim

Song

et al. 2021

IEEE Trans. Visual. Comput. Graphics

View full text Add to dashboard Cite

Fig. 1. Githru system. (a) The Global Temporal Filter shows commit trends by number of commits and CLOC (changed lines of code). (b) The Clustering Step controls the granularity of clustering. (c) The stem graph visualizes a cluster information of each commit at a single glance. (d) The Grouped Summary View provides a rough summary of the selected clusters. (e) A file icicle tree allows users to interactively observe the modified file hierarchy. (f) The commit list shows all the commits in a selected cluster. (g) Comparison View enables a comparison between selected groups.

show abstract

“…In comparison to projects that do not use CI, these projects (i) release twice as often, (ii) accept pull requests faster, and (iii) developers are less worried about breaking the build [28]. Recent studies investigated bots seeking to automate repetitive tasks in the social collaboration platform such as GitHub [36,58,59]. For example, the Hound bot was invented to verify code style violations [58].…”

Section: Related Workmentioning

confidence: 99%

Scaling open source communities

Tan

Zhou

Fitzgerald

2020

Proceedings of the ACM/IEEE 42nd International Conference on Software Engineering

View full text Add to dashboard Cite

show abstract

Should I Stale or Should I Close? An Analysis of a Bot That Closes Abandoned Issues and Pull Requests

Cited by 29 publications

References 19 publications

An empirical study of bots in software development: characteristics and challenges from a practitioner’s perspective

An empirical study of bots in software development: characteristics and challenges from a practitioner’s perspective

Githru: Visual Analytics for Understanding Software Development History Through Git Metadata Analysis

Scaling open source communities

Contact Info

Product

Resources

About