openrewrite / openrewrite/rewrite-github-actions
Change Gradle commands to use the Gradle Wrapper
Open
Nobody has claimed this yet.
recipe
- Dominant language
- Java
- Stars
- 1
- Forks
- 9
- Avg merge
- 5h 27m
- Merged PRs (30d)
- 12
Description
Example:
name: Java CI
on: [push]
jobs:
build:
runs-on: ubuntu-latest
steps:
- name: Build with gradle
run: gradle test
Unix runners:
name: Java CI
on: [push]
jobs:
build:
runs-on: ubuntu-latest
steps:
- name: Build with gradle
run: ./gradlew test
Windows Runners:
name: Java CI
on: [push]
jobs:
build:
runs-on: ubuntu-latest
steps:
- name: Build with gradle
run: gradlew test
Same as https://github.com/openrewrite/rewrite-github-actions/issues/57 but with the Gradle Wrapper
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing this request with the related issue #57 and locate the GitHub Actions recipe that emits Gradle commands. Use the supplied Unix and Windows examples as the expected forms; done means generated workflows use ./gradlew on Unix runners and gradlew on Windows runners.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, java
- Domain
- build-system, ci-cd
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100