Dependency update bots automatically open pull requests to update software dependencies on behalf of developers. Early research shows that developers are suspicious of updates performed by bots and feel tired of overwhelming notifications from these bots. Despite this, dependency update bots are becoming increasingly popular. Such contrast motivates us to investigate Dependabot, currently the most visible bot in GitHub, to reveal the effectiveness and limitations of the state-of-art dependency update bots. We use exploratory data analysis and developer survey to evaluate the effectiveness of Dependabot in keeping dependencies up-to-date, reducing update suspicion, and reducing notification fatigue. We obtain mixed findings. On the positive side, Dependabot is effective in reducing technical lag and developers are highly receptive to its pull requests. On the negative side, its compatibility scores are too scarce to be effective in reducing update suspicion; developers tend to configure Dependabot toward reducing the number of notifications; and 11.3\% of projects have deprecated Dependabot in favor of other alternatives. Our findings reveal a large room for improvement in dependency update bots which calls for effort from both bot designers and software engineering researchers.
翻译:早期研究表明,开发商对机器人进行的最新更新感到怀疑,对来自这些机器人的压倒性通知感到厌烦。尽管如此,依赖性更新机器人越来越受欢迎。这种对比促使我们调查目前GitHub中最可见的机体Deptabot, 以揭示最新依赖性更新机体的有效性和局限性。我们利用探索性数据分析和开发者调查来评价依赖性设计公司在不断更新、减少新的怀疑和减少通知疲劳方面的有效性。我们得到的结果好坏参半。在正面方面,Dependabot在减少技术滞后方面是有效的,开发商对它的拉动要求非常接受。在负面方面,它的兼容性分数太少,无法有效减少新的怀疑;开发商倾向于配置依赖性设计软件更新机体,以减少通知的数量;11.3%的项目在更新软件设计师和软件设计师的努力方面都出现了很大的改进空间。