Add CI configuration recipes with screenshots to contributing.md. (#15331)
Hoping to clarify the process (e.g. [this Discord
discussion](https://discord.com/channels/689900678990135345/689957613152239638/1167552939418714202))
diff --git a/docs/developers/assets/ci-extra.png b/docs/developers/assets/ci-extra.png
new file mode 100644
index 0000000..f6c3573
--- /dev/null
+++ b/docs/developers/assets/ci-extra.png
Binary files differ
diff --git a/docs/developers/assets/ci_enabled_jobs.png b/docs/developers/assets/ci_enabled_jobs.png
new file mode 100644
index 0000000..f92be6f
--- /dev/null
+++ b/docs/developers/assets/ci_enabled_jobs.png
Binary files differ
diff --git a/docs/developers/developing_iree/contributing.md b/docs/developers/developing_iree/contributing.md
index 05a076a..d5774eb 100644
--- a/docs/developers/developing_iree/contributing.md
+++ b/docs/developers/developing_iree/contributing.md
@@ -96,3 +96,40 @@
self-hosted runners. We maintain a test environment to allow testing out new
configurations prior to rolling them out. This trailer is for advanced users who
are working on the CI infrastructure itself.
+
+#### CI configuration recipes
+
+Copy/paste any of these at the bottom of a PR description to change what the CI
+runs.
+
+* Also run Windows and macOS builds that are normally post-merge only:
+
+ ``` text
+ ci-extra: build_test_all_windows,build_test_all_macos_arm64,build_test_all_macos_x86_64
+ ```
+
+* Also run GPU tests on NVIDIA A100 runners (opt-in due to low availability):
+
+ ``` text
+ ci-extra: test_a100
+ ```
+
+* Skip all CI builds and tests, e.g. for comment-only changes:
+
+ ``` text
+ skip-ci: Comment-only change.
+ ```
+
+* Only run Bazel builds, e.g. for changes only affecting Bazel rules:
+
+ ``` text
+ ci-exactly: build_test_all_bazel
+ ```
+
+For example, this PR opted in to running the `build_test_all_windows` job:
+
+
+
+The enabled jobs can be viewed from the Summary page of an action run:
+
+
