From 4bbbfe4ceb82d09284f794fa3a4390bf994f4351 Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Sat, 21 Feb 2026 02:16:48 +0000
Subject: [PATCH 1/2] Initial plan


From a06604c7ea433d4f185ea0f333efa3a14b2afa23 Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Sat, 21 Feb 2026 02:34:08 +0000
Subject: [PATCH 2/2] Remove orchestrator-only sections from gh aw logs --help

Removes the 'Orchestrator Usage' and 'Live Tracking with Project Boards'
sections from the logs command's Long description. These contained
YAML snippets and 'DO NOT call' warnings intended for AI orchestrator
workflows, not human CLI users. Updates the test to match.

Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
---
 pkg/cli/logs_command.go      | 32 --------------------------------
 pkg/cli/logs_command_test.go |  2 +-
 2 files changed, 1 insertion(+), 33 deletions(-)

diff --git a/pkg/cli/logs_command.go b/pkg/cli/logs_command.go
index 84fe62934f1..ad31b1a8018 100644
--- a/pkg/cli/logs_command.go
+++ b/pkg/cli/logs_command.go
@@ -44,38 +44,6 @@ Downloaded artifacts include:
 - workflow-logs/: GitHub Actions workflow run logs (job logs organized in subdirectory)
 - summary.json: Complete metrics and run data for all downloaded runs
 
-Orchestrator Usage:
-	In an orchestrator workflow, use this command in a pre-step to download logs,
-  then access the data in subsequent steps without needing GitHub CLI access:
-
-    steps:
-      - name: Download logs from last 30 days
-        env:
-          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-        run: |
-          mkdir -p /tmp/portfolio-logs
-          gh aw logs <worker> --start-date -1mo -o /tmp/portfolio-logs
-
-  In your analysis step, reference the pre-downloaded data:
-    
-    **All workflow execution data has been pre-downloaded for you in the previous workflow step.**
-    
-    - **JSON Summary**: /tmp/portfolio-logs/summary.json - Contains all metrics and run data you need
-    - **Run Logs**: /tmp/portfolio-logs/run-{database-id}/ - Individual run logs (if needed for detailed analysis)
-    
-    **DO NOT call 'gh aw logs' or any GitHub CLI commands** - they will not work in your environment.
-    All data you need is in the summary.json file.
-
-	Live Tracking with Project Boards:
-		Use the summary.json data to update your project board, treating issues/PRs (workers)
-		on the board as the real-time view of progress, ownership, and status. The orchestrator workflow
-		can use the 'update-project' safe output to sync status fields without modifying worker workflow
-		files. Workers remain unchanged while the board reflects current execution state.
-    
-    For incremental updates, pull data for each worker based on the last pull time using --start-date
-    (e.g., --start-date -1d for daily updates) and align with existing board items. Compare run data
-    from summary.json with board status to update only changed workers, preserving board state.
-
 ` + WorkflowIDExplanation + `
 
 Examples:
diff --git a/pkg/cli/logs_command_test.go b/pkg/cli/logs_command_test.go
index 70398f04e28..434dc5eb1af 100644
--- a/pkg/cli/logs_command_test.go
+++ b/pkg/cli/logs_command_test.go
@@ -248,7 +248,7 @@ func TestLogsCommandHelpText(t *testing.T) {
 	// Verify long description contains expected sections
 	expectedSections := []string{
 		"Download workflow run logs",
-		"Orchestrator Usage",
+		"Downloaded artifacts include:",
 		"Examples:",
 		"gh aw logs",
 	}