Skip to content

refactor: JUnit Jupiter migration from JUnit 4.x #2590

refactor: JUnit Jupiter migration from JUnit 4.x

refactor: JUnit Jupiter migration from JUnit 4.x #2590

Triggered via pull request November 15, 2024 09:42
Status Failure
Total duration 24s
Artifacts

commitlint.yml

on: pull_request
commitlint
14s
commitlint
Fit to window
Zoom out
Zoom in

Annotations

1 error and 3 warnings
commitlint
You have commit messages with errors ⧗ input: refactor: JUnit Jupiter migration from JUnit 4.x Use this link to re-run the recipe: https://app.moderne.io/recipes/org.openrewrite.java.testing.junit5.JUnit4to5Migration?organizationId=U0FQ Co-authored-by: Moderne <[email protected]> ✖ subject must not be sentence-case, start-case, pascal-case, upper-case [subject-case] ✖ found 1 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint
commitlint
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
commitlint
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
commitlint
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/