@@ -108,11 +108,28 @@ by looking in the `if` statements of jobs. For example you can see some
108
108
Below are commonly used ones:
109
109
110
110
111
- | ---------------------------| ---------------------------------|
112
- | ` [skip ci] ` | Skip the entire CI |
113
- | ` [skip community_build] ` | Skip the entire community build |
114
- | ` [skip community_build_a] ` | Skip the "a" community build |
115
- | ` [skip docs] ` | Skip the scaladoc tests |
111
+ | ---------------------------| ----------------------------------------|
112
+ | ` [skip ci] ` | Skip the entire CI |
113
+ | ` [skip community_build] ` | Skip the entire community build |
114
+ | ` [skip community_build_a] ` | Skip the "a" community build |
115
+ | ` [skip community_build_b] ` | Skip the "b" community build |
116
+ | ` [skip community_build_c] ` | Skip the "c" community build |
117
+ | ` [skip docs] ` | Skip the scaladoc tests |
118
+ | ` [skip test] ` | Skip the unit tests |
119
+ | ` [skip test_windows_fast] ` | Skip the unit tests subset on Windows |
120
+ | ` [skip mima] ` | Skip the MiMa checks |
121
+ | ` [skip test_sbt] ` | Skip the SBT scripted tests |
122
+
123
+
124
+ #### Executes parts of the CI that are skipped on PRs
125
+ Depending on what your PR is addressing, sometimes it doesn't make sense to run
126
+ parts of the CI that usually ony runs on nightly builds.
127
+
128
+ | ---------------------------| ----------------------------------------------------|
129
+ | ` [test_java8] ` | Execute unit tests on Java 8 |
130
+ | ` [test_windows_full] ` | Execute unit tests on Windows |
131
+ | ` [test_non_bootstrapped] ` | Execute unit tests using non-bootstrapped compiler |
132
+
116
133
117
134
#### Making sure every commit triggers a new run
118
135
0 commit comments