From 415689323c625afb7d39d923c4165a541beb9927 Mon Sep 17 00:00:00 2001
From: flywind <43030857+xflywind@users.noreply.github.com>
Date: Thu, 9 Jun 2022 00:17:25 +0800
Subject: [PATCH] clarify how to restart CI (#19845)

---
 doc/contributing.rst | 1 +
 1 file changed, 1 insertion(+)

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