How Do Software Developers Use GitHub Actions to Automate Their Workflows?

@article{Kinsman2021HowDS,
  title={How Do Software Developers Use GitHub Actions to Automate Their Workflows?},
  author={Timothy Kinsman and Mairieli Santos Wessel and Marco Aur{\'e}lio Gerosa and Christoph Treude},
  journal={2021 IEEE/ACM 18th International Conference on Mining Software Repositories (MSR)},
  year={2021},
  pages={420-431}
}
Automated tools are frequently used in social coding repositories to perform repetitive activities that are part of the distributed software development process. Recently, GitHub introduced GitHub Actions, a feature providing automated work-flows for repository maintainers. Although several Actions have been built and used by practitioners, relatively little has been done to evaluate them. Understanding and anticipating the effects of adopting such kind of technology is important for planning… 
GitHub Actions: The Impact on the Pull Request Process
TLDR
This research investigates how projects use GitHub Actions, what the communities discuss about them, and how activity indicators change after their adoption, and provides empirical data on which GitHub Actions are currently used and what their impact can be on development processes.
Quality Gatekeepers: Investigating the Effects ofCode Review Bots on Pull Request Activities
TLDR
The results indicate that the adoption of code review bots increases the number of monthly merged pull requests, decreases monthly non-mergedPull requests, and decreases communication among developers.
On the rise and fall of CI services in GitHub
TLDR
A longitudinal empirical study over a period of nine years quantitatively studied the evolution of seven popular CIs, specifically focusing on their co-usage and migration in the considered repositories, providing statistical evidence of the rise of GitHub Actions.
Advantages of maintaining a multi-task project-specific bot: an experience report
TLDR
The kind of automation that the Coq project bot implements, what advantages the team has gained by maintaining a project-specific bot, and the technology and architecture choices that have made it possible are described.
An Analysis of Automated Code Inspection Tools for PHP Available on Github Marketplace
TLDR
This article proposes to analyze code inspection tools for PHP programming language, freely available on Github Marketplace, and finds more than ten thousand failures divided into thirty-four different CWEs and analyzes the individual feedback of each tool.
Don't Disturb Me: Challenges of Interacting with Software Bots on Open Source Software Projects
TLDR
The main contribution is a theory of how human developers perceive annoying bot behaviors as noise on social coding platforms to help practitioners understand the effects of adopting a bot and researchers and tool designers may leverage the results to better support human-bot interaction on social code platforms.
Automatically Categorising GitHub Repositories by Application Domain
TLDR
This work builds on a previously annotated dataset of 5,000 GitHub repositories to design an automated classifier for categorising repositories by their application domain and opens promising avenues for future work investigating differences between repositories from di⬀erent application domains.
Bots in software engineering: a systematic mapping study
TLDR
This study focuses on classification of bots used in software engineering, the various dimensions of the characteristics, the more frequently researched area, potential research spaces to be explored and the perception of bots in the developer community.
Using Benchmarking Bots for Continuous Performance Assessment
TLDR
How and why projects use benchmarking bots are discussed, and an in- depth case study of The Nanosoldier bot used by the team behind the Julia programming language is presented.
ery-Analysis on Git-A ributes in Relational and Graph-DB
  • 2022
...
...

References

SHOWING 1-10 OF 38 REFERENCES
Tool Choice Matters: JavaScript Quality Assurance Tools and Usage Outcomes in GitHub Projects
TLDR
A general methodology to model the time- dependent effect of automation tool choice on four outcomes of interest: prevalence of issues, code churn, number of pull requests, and number of contributors, all with a multitude of controls.
Work practices and challenges in pull-based development: the contributor's perspective
TLDR
This research examines the work practices of project contributors and the challenges they face within the pull-based development model by conducting a survey with top contributors to active OSS projects on GitHub.
The Silent Helper: The Impact of Continuous Integration on Code Reviews
TLDR
An exploratory study of code reviews in 685 GitHub projects that have adopted Travis-CI, the most popular CI-service on GitHub observes that with the introduction of CI, pull requests are being discussed less, giving rise to the idea of CI as a silent helper.
An exploratory study of the pull-based software development model
TLDR
This work explores how pull-based software development works, first on the GHTorrent corpus and then on a carefully selected sample of 291 projects, finding that the pull request model offers fast turnaround, increased opportunities for community engagement and decreased time to incorporate contributions.
The impact of continuous integration on other software development practices: A large-scale empirical study
TLDR
The adaptation and evolution of code writing and submission, issue and pull request closing, and testing practices as Travis CI is adopted by hundreds of established projects on GitHub are studied to suggest a more nuanced picture of how GitHub teams are adapting to, and benefiting from, continuous integration technology.
Towards an Autonomous Bot for Automatic Source Code Refactoring
  • Marvin WyrichJ. Bogner
  • Computer Science
    2019 IEEE/ACM 1st International Workshop on Bots in Software Engineering (BotSE)
  • 2019
TLDR
The Refactoring-Bot is presented, an autonomous bot that integrates into the team like a human developer via the existing version control platform and automatically performs refactorings to resolve code smells and presents the changes to a developer for asynchronous review via pull requests.
The promises and perils of mining GitHub
TLDR
It is shown, for example, that the majority of the projects are personal and inactive; that GitHub is also being used for free storage and as a Web hosting service; and that almost 40% of all pull requests do not appear as merged, even though they were.
Disrupting developer productivity one bot at a time
TLDR
The modern Bot landscape is outlined and a preliminary cognitive support framework is proposed that can be used to understand these roles and to reflect on the impact of Bots in software development on productivity.
Quality and productivity outcomes relating to continuous integration in GitHub
TLDR
The main finding is that continuous integration improves the productivity of project teams, who can integrate more outside contributions, without an observable diminishment in code quality.
Effects of Adopting Code Review Bots on Pull Requests to OSS Projects
TLDR
This work investigates how several activity indicators change after the adoption of a code review bot and employs a regression discontinuity design to understand, or even predict, bot effects on their projects’ social interactions.
...
...