feat(gradle-build-pr): add run-tests flag for BOM and test-less projects#10
Merged
Merged
Conversation
Add a `run-tests` boolean input (default `true`) so the same workflow can be reused for projects with tests, projects without tests, and BOM-only publications. When `run-tests` is false the JUnit upload step and the aggregation job are skipped, and the resolved gradle task falls back from `build test` to `build`. Existing consumers keep their current behavior.
…lint markdownlint flags MD012 (multiple consecutive blank lines) on every release-please-generated CHANGELOG.md entry. Add a markdownlint-cli2 config that ignores the file — release-please owns the formatting. lychee gets a 403 from Cloudflare on docs.renovatebot.com even though the page resolves fine in browsers. Add the host to .lycheeignore so the link check stops failing on a healthy URL.
lychee 0.23 removed --exclude-mail (mail isn't checked unless --include-mail is passed). The lychee-action v2 ships lychee 0.23.0 since the last bump, so the default lychee-args were rejected as "unexpected argument". Drop the flag — behavior is unchanged.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
run-tests(defaulttrue) amgradle-build-pr-Workflow, damit dasselbe reusable Workflow für drei Projekt-Klassen funktioniert: Projekte mit Tests, ohne Tests und reine BOMs (java-platform).run-tests: false: der JUnit-Upload-Step und dertest-report-Aggregations-Job werden geskippt — kein leerer Check, kein „No test results found"-PR-Comment mehr.gradle-taskwird zur Laufzeit ausinputs.gradle-task(falls gesetzt), sonst ausrun-testsaufgelöst (build testbeitrue,buildbeifalse). Default-Input ist jetzt leer; explizite Werte überschreiben die Auflösung weiterhin.Bestehende Consumer brauchen keine Anpassung — Default-Verhalten ist identisch zu v2.0.1.
Outline-Doku ebenfalls aktualisiert:
run-tests-Eintrag + Globale-Defaults-Tabelle)Test plan
test-report-Job muss weiterhin Tests aggregieren.run-tests: falsepinnen, PR-Build muss grün laufen,test-report-Job darf nicht erscheinen, keinetest-reports-*-Artefakte werden hochgeladen.feat:-Commit einen Minor-Bump →v2.1.0.Generated by Claude Code