How Do Software Developers Use GitHub Actions to Automate Their Workflows?
Fuente:
arXiv
Gespeichert in:
| Hauptverfasser: | , , , |
|---|---|
| Format: | Preprint |
| Veröffentlicht: |
2021
|
| Schlagworte: | |
| Online-Zugang: | |
| Tags: |
Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
|
| _version_ | 1866929218542108672 |
|---|---|
| author | Kinsman, Timothy Wessel, Mairieli Gerosa, Marco A. Treude, Christoph |
| author_facet | Kinsman, Timothy Wessel, Mairieli Gerosa, Marco A. Treude, Christoph |
| contents | 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 workflows 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 and management. Our research is the first to investigate how developers use Actions and how several activity indicators change after their adoption. Our results indicate that, although only a small subset of repositories adopted GitHub Actions to date, there is a positive perception of the technology. Our findings also indicate that the adoption of GitHub Actions increases the number of monthly rejected pull requests and decreases the monthly number of commits on merged pull requests. These results are especially relevant for practitioners to understand and prevent undesirable effects on their projects. |
| format | Preprint |
| id |
arxiv_https___arxiv_org_abs_2103_12224 |
| institution | arXiv |
| publishDate | 2021 |
| record_format | arxiv |
| spellingShingle | How Do Software Developers Use GitHub Actions to Automate Their Workflows? Kinsman, Timothy Wessel, Mairieli Gerosa, Marco A. Treude, Christoph Software Engineering 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 workflows 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 and management. Our research is the first to investigate how developers use Actions and how several activity indicators change after their adoption. Our results indicate that, although only a small subset of repositories adopted GitHub Actions to date, there is a positive perception of the technology. Our findings also indicate that the adoption of GitHub Actions increases the number of monthly rejected pull requests and decreases the monthly number of commits on merged pull requests. These results are especially relevant for practitioners to understand and prevent undesirable effects on their projects. |
| title | How Do Software Developers Use GitHub Actions to Automate Their Workflows? |
| topic | Software Engineering |
| url | https://arxiv.org/abs/2103.12224 |