# gradle/actions in GitHub Actions Workflows

DevFeed: [gradle/actions in GitHub Actions Workflows](<https://devfeed.tech/articles/you-are-probably-already-running-gradle-actions-24690.md>)

Original publisher: [Read original article](<https://blog.gradle.org/running-gradle-github-actions>)

Author: Laura Kassovic

Published: 2026-06-30T04:00:00Z

Content type: opinion

Language: en

Sources: [The Gradle Blog](<https://devfeed.tech/sources/the-gradle-blog.md>)

Topics: [Gradle](<https://devfeed.tech/topics/gradle.md>), [GitHub Actions](<https://devfeed.tech/topics/github-actions.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [Caching](<https://devfeed.tech/topics/caching.md>)

Tags: [caching](<https://devfeed.tech/tags/caching.md>), [github](<https://devfeed.tech/tags/github.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [gradle](<https://devfeed.tech/tags/gradle.md>)

## AI overview

An opinionated primer on gradle/actions, especially setup-gradle, which helps Gradle run in ephemeral GitHub Actions runners. It discusses the action's adoption and the importance of caching Gradle state in CI.

## Source excerpt

There is a particular kind of software that you depend on heavily and have never once thought about. It does not have a landing page you have visited. It was not chosen at an architecture review. Nobody sat in a conference room and debated it against three competitors, and no one wrote a blog post titled "Why We Migrated To It." It simply showed up one day, did its job, and has been doing its job on every commit since. A great deal of the build automation running on GitHub is this kind of software. And one of the most widely used examples, if you write anything that touches the Java Virtual Machine, is a small collection of GitHub Actions published by Gradle at gradle/actions. You may not recognize the name setup-gradle. But it's used by more than 45,000 open source repositories, and it's the action baked into GitHub's own official starter workflow for Gradle projects. When you click "Set up a workflow" on a fresh Gradle repo and accept the suggestion GitHub hands you, you are adopting gradle/actions without ever having formed an opinion about it. This is how the most consequential defaults always spread: not by persuasion but by presumption. It is the same mechanism by which much of Europe enrolls organ donors. So: a primer on what the thing does, a tour of who actually runs it in production, and an argument about why the unglamorous parts are the ones worth caring about. What it actually is gradle/actions is not one action. It is a small family of them, and in practice, almost everyone means the same one when they invoke it. The centerpiece is setup-gradle. Its job is to make Gradle run well inside a GitHub Actions runner, which is a fresh, ephemeral machine that has never heard of your project and will be deleted the moment your build finishes. Left to its own devices, that machine re-downloads your dependencies, re-initializes Gradle, and re-does a pile of work it has no memory of having done five minutes ago on the previous commit. setup-gradle is what gives th