diff options
| author | flywind <43030857+xflywind@users.noreply.github.com> | 2022-06-09 00:17:25 +0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-06-08 18:17:25 +0200 |
| commit | 415689323c625afb7d39d923c4165a541beb9927 (patch) | |
| tree | c6c61b51ac1cd16c748085f564a0e3ca97f3815c /doc | |
| parent | e1702ae1e6da5bf560d7b692bcd5fa513ece8a69 (diff) | |
| download | Nim-415689323c625afb7d39d923c4165a541beb9927.tar.gz | |
clarify how to restart CI (#19845)
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/contributing.rst | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/doc/contributing.rst b/doc/contributing.rst index d3b2770f3..0ca0d0cbc 100644 --- a/doc/contributing.rst +++ b/doc/contributing.rst @@ -539,6 +539,7 @@ Debugging CI failures, flaky tests, etc 2. If CI failure seems unrelated to your PR, it could be caused by a flaky test. File a bug for it if it isn't already reported. A PR push (or opening/closing PR) will re-trigger all CI jobs (even successful ones, which can be wasteful). Instead, + request collaboration from the Nim team. The Nim team should follow these instructions to only restart the jobs that failed: * Azure: if on your own fork, it's possible from inside azure console |