From d0ba751dafc0d7f4a4c10c951d5583b9ac188a3f Mon Sep 17 00:00:00 2001
From: Matt C <41025489+mcummings128@users.noreply.github.com>
Date: Tue, 5 May 2026 00:05:18 -0400
Subject: [PATCH] Mod instructions enabling debug logging: orgs

Clarified that the secret or variable can be set at the organizational level for enabling runner and step debug logging. As in, you can set ACTIONS_RUNNER_DEBUG to true at organization-level and it will work as expected.
---
 .../actions/how-tos/monitor-workflows/enable-debug-logging.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/content/actions/how-tos/monitor-workflows/enable-debug-logging.md b/content/actions/how-tos/monitor-workflows/enable-debug-logging.md
index bfde82cb51ba..ac22dc9915c3 100644
--- a/content/actions/how-tos/monitor-workflows/enable-debug-logging.md
+++ b/content/actions/how-tos/monitor-workflows/enable-debug-logging.md
@@ -36,14 +36,14 @@ Runner diagnostic logging provides additional log files that contain information
 * The runner process log, which includes information about coordinating and setting up runners to execute jobs.
 * The worker process log, which logs the execution of a job.
 
-1. To enable runner diagnostic logging, set the following secret or variable in the repository that contains the workflow: `ACTIONS_RUNNER_DEBUG` to `true`. If both the secret and variable are set, the value of the secret takes precedence over the variable.
+1. To enable runner diagnostic logging, set the following secret or variable in the repository (or at organizational-level) that contains the workflow: `ACTIONS_RUNNER_DEBUG` to `true`. If both the secret and variable are set, the value of the secret takes precedence over the variable.
 1. To download runner diagnostic logs, download the log archive of the workflow run. The runner diagnostic logs are contained in the `runner-diagnostic-logs` folder. For more information on downloading logs, see [AUTOTITLE](/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs#downloading-logs).
 
 ## Enabling step debug logging
 
 Step debug logging increases the verbosity of a job's logs during and after a job's execution.
 
-1. To enable step debug logging, set the following secret or variable in the repository that contains the workflow: `ACTIONS_STEP_DEBUG` to `true`. If both the secret and variable are set, the value of the secret takes precedence over the variable.
+1. To enable step debug logging, set the following secret or variable in the repository (or at organizational-level) that contains the workflow: `ACTIONS_STEP_DEBUG` to `true`. If both the secret and variable are set, the value of the secret takes precedence over the variable.
 1. After setting the secret or variable, more debug events are shown in the step logs. For more information, see [AUTOTITLE](/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs#viewing-logs-to-diagnose-failures).
 
 You can also use the `runner.debug` context to conditionally run steps only when debug logging is enabled. For more information, see [AUTOTITLE](/actions/reference/workflows-and-actions/contexts#runner-context).