How people really use GitHub Actions
summary
Study of 3000 projects finds 700 actions across 20 categories and shows typical actions are added twice and then rarely changed, turning automation into a lasting dependency. Adding Actions correlates with an increase in rejected contributions and fewer commits per merged PR. Analysis uses repository configuration mining and discussion-text coding and recommends measuring code performance, contribution volume, and communication before and after adoption to spot unexpected workflow or social effects.
AI-written summary · about
chapters (8)
- 0:00Intro
- 1:11GitHub Workflow automation with GitHub Actions
- 1:48The Gammapy example: Greetings action
- 2:26Usage of GitHub Actions
- 3:48Discussions about GitHub Actions
- 5:14Impacts of GitHub Actions usage
- 6:23Perception vs. Reality
- 7:21What can you do?
related talks
36mGitHub Actions: Open Source Workflow Automation
42mThere’s an Action for That! Exploring the Possibilities of GitHub Actions
01h 47mDeveloper Workflow Automation with GitHub Actions
01h 01mGetting Started with GitHub Actions
32mHacker Traction Through GitHub Actions: Is Your (Open Source) Project Safe?
24mGitHub Actions in Action
05mMaking Awesome Automations with GitHub Actions
25mAutomate Maintainer Tasks With GitHub Actions