From 3458be4028c46f0e503825daf636ab0391271d9e Mon Sep 17 00:00:00 2001 From: Stan Brubaker <120737309+stanbrub@users.noreply.github.com> Date: Fri, 17 Jan 2025 17:01:20 -0700 Subject: [PATCH] Update AdhocWorkflows.md --- docs/AdhocWorkflows.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/AdhocWorkflows.md b/docs/AdhocWorkflows.md index b8c2075..af26058 100644 --- a/docs/AdhocWorkflows.md +++ b/docs/AdhocWorkflows.md @@ -14,7 +14,7 @@ Prerequisites: ### Starting a Benchmark Run -The typical Benchmark run will be initiated from a Github on-demand workflow action in the main [Deephaven Benchmark](https://github.com/deephaven/benchmark/actions). However, the "Adhoc" workflows can be run from a fork as well, assuming the correct privileges are set up. (This is outside the scope of this document.) +The typical Benchmark run will be initiated from a [Github on-demand workflow](https://docs.github.com/en/actions/managing-workflow-runs-and-deployments/managing-workflow-runs/manually-running-a-workflow) action in the main [Deephaven Benchmark](https://github.com/deephaven/benchmark/actions). However, the "Adhoc" workflows can be run from a fork as well, assuming the correct privileges are set up. (This is outside the scope of this document.) There are two Adhoc Workflows: - [Adhoc Benchmarks (Auto-provisioned Server)](https://github.com/deephaven/benchmark/actions/workflows/adhoc-auto-remote-benchmarks.yml)