No description
Find a file
daz 9e47918adf Build and commit changes to 'dist' automatically
Instead of requiring that developers keep the 'dist' directory up-to-date,
this process is now automated via a workflow.
Whenever a commit is pushed to 'main' (or a 'release/**' branch), the workflow will
build the application and commit any changes to the 'dist' directory.
2024-04-10 07:33:46 -06:00
.github Build and commit changes to 'dist' automatically 2024-04-10 07:33:46 -06:00
dependency-submission Allow a task name to be specified for dependency-submission 2024-04-09 08:46:20 -06:00
dist Build outputs 2024-04-09 15:30:42 -06:00
docs Improve deprecation-upgrade-guide 2024-04-09 16:06:46 -06:00
setup-gradle Use consistent action params between setup-gradle and dependency-submission 2024-04-07 12:11:50 -06:00
sources Build and commit changes to 'dist' automatically 2024-04-10 07:33:46 -06:00
.gitignore Ignore VScode config files 2024-03-21 21:52:16 -06:00
action.yml Move top-level action to 'setup-gradle' 2024-01-25 11:53:44 -07:00
build Replace sources/build with top-level ./build script 2024-04-07 16:57:18 -06:00
CODE_OF_CONDUCT.md add code of conduct 2019-09-21 20:57:04 +02:00
CONTRIBUTING.md Minor test reorg 2024-04-06 16:00:53 -06:00
LICENSE Update copyright notice 2023-06-30 08:57:49 -06:00
README.md Add 'setup-java' step to all examples 2024-04-05 14:54:29 -06:00
RELEASING.md Documentation improvements (#132) 2024-04-08 19:19:50 -06:00

GitHub Actions for Gradle builds

This repository contains a set of GitHub Actions that are useful for building Gradle projects on GitHub.

The setup-gradle action

The setup-gradle action can be used to configure Gradle for optimal execution on any platform supported by GitHub Actions.

This replaces the previous gradle/gradle-build-action, which now delegates to this implementation.

The recommended way to execute any Gradle build is with the help of the Gradle Wrapper, and the examples assume that the Gradle Wrapper has been configured for the project. See this example if your project doesn't use the Gradle Wrapper.

Example usage

name: Build

on: [ push ]

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
    - name: Checkout sources
      uses: actions/checkout@v4
    - name: Setup Java
      uses: actions/setup-java@v4
      with:
        distribution: 'temurin'
        java-version: 17
    - name: Setup Gradle
      uses: gradle/actions/setup-gradle@v3
    - name: Build with Gradle
      run: ./gradlew build

See the full action documentation for more advanced usage scenarios.

The dependency-submission action

Generates and submits a dependency graph for a Gradle project, allowing GitHub to alert about reported vulnerabilities in your project dependencies.

The following workflow will generate a dependency graph for a Gradle project and submit it immediately to the repository via the Dependency Submission API. For most projects, this default configuration should be all that you need.

Simply add this as a new workflow file to your repository (eg .github/workflows/dependency-submission.yml).

name: Dependency Submission

on: [ push ]

permissions:
  contents: write

jobs:
  dependency-submission:
    runs-on: ubuntu-latest
    steps:
    - name: Checkout sources
      uses: actions/checkout@v4
    - name: Setup Java
      uses: actions/setup-java@v4
      with:
        distribution: 'temurin'
        java-version: 17
    - name: Generate and submit dependency graph
      uses: gradle/actions/dependency-submission@v3

See the full action documentation for more advanced usage scenarios.