From e8273cac1178edfcc928ae1ddb3efcc63fe9f99c Mon Sep 17 00:00:00 2001
From: Noel Kwan <47273164+kwannoel@users.noreply.github.com>
Date: Wed, 17 Jul 2024 17:38:34 +0800
Subject: [PATCH] doc: fix `main-cron-bisect` docs (#17720)

---
 docs/dev/src/ci.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/docs/dev/src/ci.md b/docs/dev/src/ci.md
index 0f12d893acae..1a34374cc324 100644
--- a/docs/dev/src/ci.md
+++ b/docs/dev/src/ci.md
@@ -22,20 +22,20 @@ To run `e2e-test` and `e2e-source-test` for `main-cron` in your pull request:
 
 ## Main Cron Bisect Guide
 
-1. Create a new build via buildkite: https://buildkite.com/risingwavelabs/main-cron-bisect/builds/#new
+1. Create a new build via [buildkite](https://buildkite.com/risingwavelabs/main-cron-bisect/builds/#new)
 2. Add the following environment variables:
    - `GOOD_COMMIT`: The good commit hash.
    - `BAD_COMMIT`: The bad commit hash.
    - `BISECT_BRANCH`: The branch name where the bisect will be performed.
    - `CI_STEPS`: The `CI_STEPS` to run during the bisect. Separate multiple steps with a comma.
-     - You can check the labels for this in `main-cron.yml`, under the conditions for each step.
+     - You can check the labels for this in [main-cron.yml](https://github.com/risingwavelabs/risingwave/blob/main/ci/workflows/main-cron.yml),
+       under the conditions for each step.
 
 Example you can try on [buildkite](https://buildkite.com/risingwavelabs/main-cron-bisect/builds/#new):
-- Branch: `kwannoel/find-regress`
 - Environment variables:
   ```
-  START_COMMIT=29791ddf16fdf2c2e83ad3a58215f434e610f89a
-  END_COMMIT=7f36bf17c1d19a1e6b2cdb90491d3c08ae8b0004
+  GOOD_COMMIT=29791ddf16fdf2c2e83ad3a58215f434e610f89a
+  BAD_COMMIT=7f36bf17c1d19a1e6b2cdb90491d3c08ae8b0004
   BISECT_BRANCH=kwannoel/test-bisect
   CI_STEPS="test-bisect,disable-build"
   ```
\ No newline at end of file