Update CI script to properly fail if `projectHealth` gradle task has dependencies to fix

Open
#67 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
kotlin

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.

Description

https://github.com/assertj/assertj-generator-gradle-plugin/pull/66 shows a failing projectHealth, however it passes the CI action:
image

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 to support failing instead of passing.

Dominant language
Kotlin
Stars
34
Forks
5
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from assertj/assertj-generator-gradle-plugin

All issues in assertj/assertj-generator-gradle-plugin

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.