assertj / assertj/assertj-generator-gradle-plugin
Update CI script to properly fail if `projectHealth` gradle task has dependencies to fix
- Dominant language
- Kotlin
- Stars
- 34
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
https://github.com/assertj/assertj-generator-gradle-plugin/pull/66 shows a failing `projectHealth`, however it passes the CI action:

Example that has this support:
https://github.com/Nava2/kaff4/blob/c689f6f8d9e2552a1dc3dddaf051e1a0e2256742/.github/workflows/gradle-check-pristine.yml#L25
It _might_ be easier to add support to the [gradle plugin](https://github.com/autonomousapps/dependency-analysis-android-gradle-plugin) to support failing instead of passing.
Contributor guide
No contributing guide indexed for this repository
Research direction
Inspect the repository's GitHub Actions workflow and the projectHealth Gradle task invocation, then compare its behavior with the linked gradle-check-pristine.yml example. Confirm how dependency failures are reported and consider the linked dependency-analysis Gradle plugin before defining completion as CI failing when projectHealth has fixable dependencies.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- build-system, ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100