From 63c07a128c356a42ff01736cb9f417a2dbe99f4c Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Thu, 23 Apr 2026 13:32:19 +0000 Subject: [PATCH 1/3] Initial plan From 792c4ed01b6dcb4a1286a930e85eb16df598292a Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Thu, 23 Apr 2026 13:50:02 +0000 Subject: [PATCH 2/3] docs: add direct content verification fallback in DDUw step 1c Agent-Logs-Url: https://github.com/github/gh-aw/sessions/00e51cdd-1ba7-4dd9-8caf-0fb34361233a Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com> --- .github/workflows/daily-doc-updater.md | 5 +++++ pkg/cli/spec_test.go | 10 +++++----- 2 files changed, 10 insertions(+), 5 deletions(-) diff --git a/.github/workflows/daily-doc-updater.md b/.github/workflows/daily-doc-updater.md index 26b34ba8141..6bbfd0a12dc 100644 --- a/.github/workflows/daily-doc-updater.md +++ b/.github/workflows/daily-doc-updater.md @@ -111,6 +111,11 @@ For each closed issue: 2. Search for merged PRs in a tight window around issue closure (prefer ±60 minutes) that modify `pkg//README.md`. 3. Example query: `repo:${{ github.repository }} is:pr is:merged merged:>= merged:<= path:pkg//README.md`. 4. If such a PR exists and the README change fully resolves the issue gap, treat the issue as already addressed and skip it. + - If the fallback heuristic still finds no PR, run a direct content check before Step 2: + 1. Parse the issue body for referenced file paths and the specific missing symbols/constants/phrases. + 2. Read only those referenced files directly. + 3. Verify whether each listed gap is still present. + 4. If all listed items are already documented, treat the issue as already addressed and skip it (do not continue to Step 2 for this issue). - Otherwise, treat it as an unaddressed gap and follow the normal Step 2 flow. - **closed as not_planned**: Do not create documentation based solely on this issue. Instead, cross-reference the issue's subject matter against commits from the same 7-day window (Step 2). If a related code change is found, treat it as a new documentation gap (independent of the original issue decision) and follow the normal Step 2 flow for that code change. diff --git a/pkg/cli/spec_test.go b/pkg/cli/spec_test.go index c6b739b93fc..f46eabc88ec 100644 --- a/pkg/cli/spec_test.go +++ b/pkg/cli/spec_test.go @@ -1117,11 +1117,11 @@ func TestSpec_PublicAPI_ValidateWorkflowIntent(t *testing.T) { // Spec: "Sets a field in frontmatter YAML" func TestSpec_PublicAPI_UpdateFieldInFrontmatter(t *testing.T) { tests := []struct { - name string - content string - fieldName string - fieldValue string - wantErr bool + name string + content string + fieldName string + fieldValue string + wantErr bool checkContains string }{ { From d88e188ce64cbbae02261e1ccfb7a9e0d9a92495 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Thu, 23 Apr 2026 13:51:08 +0000 Subject: [PATCH 3/3] chore: drop unintended spec_test formatting change Agent-Logs-Url: https://github.com/github/gh-aw/sessions/00e51cdd-1ba7-4dd9-8caf-0fb34361233a Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com> --- pkg/cli/spec_test.go | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/pkg/cli/spec_test.go b/pkg/cli/spec_test.go index f46eabc88ec..c6b739b93fc 100644 --- a/pkg/cli/spec_test.go +++ b/pkg/cli/spec_test.go @@ -1117,11 +1117,11 @@ func TestSpec_PublicAPI_ValidateWorkflowIntent(t *testing.T) { // Spec: "Sets a field in frontmatter YAML" func TestSpec_PublicAPI_UpdateFieldInFrontmatter(t *testing.T) { tests := []struct { - name string - content string - fieldName string - fieldValue string - wantErr bool + name string + content string + fieldName string + fieldValue string + wantErr bool checkContains string }{ {