Adds third-party actions notices (reusable) (#58340)
This commit is contained in:
@@ -55,6 +55,7 @@ We recommend that you have a basic understanding of Java and the Gradle framewor
|
||||
If you don't find the "Java with Gradle" workflow template, copy the following workflow code to a new file called `gradle.yml` in the `.github/workflows` directory of your repository.
|
||||
|
||||
```yaml copy
|
||||
{% data reusables.actions.actions-not-certified-by-github-comment %}
|
||||
name: Java CI with Gradle
|
||||
|
||||
on:
|
||||
@@ -109,6 +110,7 @@ The workflow template will run the `build` task by default. In the default Gradl
|
||||
If you use different commands to build your project, or you want to use a different task, you can specify those. For example, you may want to run the `package` task that's configured in your `ci.gradle` file.
|
||||
|
||||
```yaml copy
|
||||
{% data reusables.actions.actions-not-certified-by-github-comment %}
|
||||
steps:
|
||||
- uses: {% data reusables.actions.action-checkout %}
|
||||
- uses: {% data reusables.actions.action-setup-java %}
|
||||
@@ -136,6 +138,7 @@ After your build has succeeded and your tests have passed, you may want to uploa
|
||||
Gradle will usually create output files like JARs, EARs, or WARs in the `build/libs` directory. You can upload the contents of that directory using the `upload-artifact` action.
|
||||
|
||||
```yaml copy
|
||||
{% data reusables.actions.actions-not-certified-by-github-comment %}
|
||||
steps:
|
||||
- uses: {% data reusables.actions.action-checkout %}
|
||||
- uses: {% data reusables.actions.action-setup-java %}
|
||||
|
||||
Reference in New Issue
Block a user