Datasets:
Fix wording
Browse files
README.md
CHANGED
@@ -45,8 +45,8 @@ Each example has the following fields:
|
|
45 |
| `original_message` | Commit message as it was in the original dataset. |
|
46 |
| `message` | Commit message cleaned from external references. |
|
47 |
| `original_label` | Commit message label as it was in the original dataset (`Why and What`/`No Why`/`No What`). |
|
48 |
-
| `is_good` | Whether the commit message serves as a good example of *high quality* (boolean). |
|
49 |
-
| `is_bad` | Whether the commit message serves as a good example of *low quality* (boolean). |
|
50 |
| `binary_label` | Commit message label: `1` for *high quality* messages, `0` for *low quality* messages, `null` for messages not recommended to consider for classifier training. |
|
51 |
|
52 |
Data point example:
|
|
|
45 |
| `original_message` | Commit message as it was in the original dataset. |
|
46 |
| `message` | Commit message cleaned from external references. |
|
47 |
| `original_label` | Commit message label as it was in the original dataset (`Why and What`/`No Why`/`No What`). |
|
48 |
+
| `is_good` | Whether the commit message serves as a good example of a *high quality* commit message (boolean). |
|
49 |
+
| `is_bad` | Whether the commit message serves as a good example of a *low quality* commit message (boolean). |
|
50 |
| `binary_label` | Commit message label: `1` for *high quality* messages, `0` for *low quality* messages, `null` for messages not recommended to consider for classifier training. |
|
51 |
|
52 |
Data point example:
|