Skip to content

Commit d75c896

Browse files
committed
docs: add in a note about [no cancel]
1 parent d53c237 commit d75c896

File tree

2 files changed

+10
-1
lines changed

2 files changed

+10
-1
lines changed

.github/workflows/ci.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ concurrency:
3131
# Taken from scalameta/metals
3232
# On main, we don't want any jobs cancelled so the sha is used to name the group
3333
# On PR branches, we cancel the job if new commits are pushed
34-
# You can also bypass that making sure[no cancel] is in your pull request body
34+
# You can also bypass that making sure [no cancel] is in your pull request body
3535
group: ${{
3636
((github.ref == 'refs/heads/main' || startsWith(github.ref, 'refs/tags'))
3737
&& format('contributor-pr-base-{0}', github.sha)

docs/_docs/contributing/sending-in-a-pr.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -114,6 +114,15 @@ Below are commonly used ones:
114114
| `[skip community_build_a]`| Skip the "a" community build |
115115
| `[skip docs]` | Skip the scaladoc tests |
116116

117+
#### Making sure every commit triggers a new run
118+
119+
By default the Dotty CI will cancel your previous runs if you push a new commit.
120+
This helps make sure the CI keeps moving without getting stuck running a ton of
121+
jobs if you push multiple times in a row. _However_, there are times you may
122+
want to run every commit. To do this, make sure your PR body contains `[no
123+
cancel]`. This will ensure that there are no cancellations of your previous
124+
runs.
125+
117126
### 7: Create your PR!
118127

119128
When the feature or fix is completed you should open a [Pull

0 commit comments

Comments
 (0)