You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: Changed-line uses LINE coverage (diff-cover); Overall/Delta use INSTRUCTION coverage (jacoco-report). The two counters are not directly comparable.
echo "_Note: Changed-line uses LINE coverage (diff-cover); Overall/Delta use INSTRUCTION coverage (jacoco-report). The two counters are not directly comparable._"
385
494
} >> "$GITHUB_STEP_SUMMARY"
386
495
387
496
# 4) Decide CI pass/fail
@@ -391,14 +500,9 @@ jobs:
391
500
exit 1
392
501
fi
393
502
394
-
if [ -z "$PR_CHANGED" ] || [ "$PR_CHANGED" = "NaN" ]; then
395
-
echo "No changed-files coverage value detected, skip changed-files gate."
396
-
exit 0
397
-
fi
398
-
399
-
if [ "$CHANGED_OK" -ne 1 ]; then
400
-
echo "Coverage gate failed: changed files coverage must be > 60%."
401
-
echo "changed=${PR_CHANGED}%"
503
+
if [ "$CHANGED_LINE_OK" -ne 1 ]; then
504
+
echo "Coverage gate failed: changed-line coverage must be > 60%."
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -147,7 +147,7 @@ We would like all developers to follow a standard development flow and coding st
147
147
2. Review the code before submission.
148
148
3. Run standardized tests.
149
149
150
-
`Sonar`-scanner and `Travis CI` continuous integration scanner will be automatically triggered when a pull request has been submitted. When a PR passes all the checks, the **java-tron** maintainers will then review the PR and offer feedback and modifications when necessary. Once adopted, the PR will be closed and merged into the `develop` branch.
150
+
`Sonar`-scanner and CI checks (GitHub Actions) will be automatically triggered when a pull request has been submitted. When a PR passes all the checks, the **java-tron** maintainers will then review the PR and offer feedback and modifications when necessary. Once adopted, the PR will be closed and merged into the `develop` branch.
151
151
152
152
We are glad to receive your pull requests and will try our best to review them as soon as we can. Any pull request is welcome, even if it is for a typo.
153
153
@@ -161,7 +161,7 @@ Please make sure your submission meets the following code style:
161
161
- The code must have passed the Sonar scanner test.
162
162
- The code has to be pulled from the `develop` branch.
163
163
- The commit message should start with a verb, whose initial should not be capitalized.
164
-
- The commit message should be less than 50 characters in length.
164
+
- The commit message title should be between 10 and 72 characters in length.
165
165
166
166
167
167
@@ -196,7 +196,7 @@ The message header is a single line that contains succinct description of the ch
196
196
The `scope` can be anything specifying place of the commit change. For example: `framework`, `api`, `tvm`, `db`, `net`. For a full list of scopes, see [Type and Scope Reference](#type-and-scope-reference). You can use `*` if there isn't a more fitting scope.
197
197
198
198
The subject contains a succinct description of the change:
199
-
1. Limit the subject line, which briefly describes the purpose of the commit, to 50 characters.
199
+
1. Limit the subject line, which briefly describes the purpose of the commit, to 72 characters (minimum 10).
200
200
2. Start with a verb and use first-person present-tense (e.g., use "change" instead of "changed" or "changes").
0 commit comments