Fix the failing GitHub Actions workflow Integration: Workflow Rendering & Bundling Analyze the workflow logs, identify the root cause of the failure, and implement a fix. Job ID: 63270126990 Job URL: https://github.com/github/gh-aw/actions/runs/2191...

[Copilot]

Fix the failing GitHub Actions workflow Integration: Workflow Rendering & Bundling

Root Cause Analysis

The test failure is caused by a mismatch between the heredoc delimiter expected by sh_integration_test.go and the actual delimiter generated by the code:

• Expected by tests: PROMPT_EOF
• Actually generated: GH_AW_PROMPT_EOF (via GenerateHeredocDelimiter("PROMPT"))

This causes all tests in sh_integration_test.go to fail because extractLinesFromYAML() cannot find any heredoc blocks, resulting in 0 chunks and 0 lines extracted.

Fix Plan

• Analyze workflow logs and identify root cause
• Update extractLinesFromYAML() to use correct delimiter GH_AW_PROMPT_EOF
• Update all test assertions that reference PROMPT_EOF to use GH_AW_PROMPT_EOF
• Run integration tests to verify fix
• Format code and commit changes
• Run full validation before final commit

Original prompt

Fix the failing GitHub Actions workflow Integration: Workflow Rendering & Bundling
Analyze the workflow logs, identify the root cause of the failure, and implement a fix.
Job ID: 63270126990
Job URL: https://github.com/github/gh-aw/actions/runs/21912473820/job/63270126990

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[Copilot]

Pull request overview

Fixes a failing integration test suite in pkg/workflow by updating test expectations to match the heredoc delimiter format produced by the workflow YAML generators (GenerateHeredocDelimiter("PROMPT") → GH_AW_PROMPT_EOF).

Changes:

• Update heredoc open/close marker assertions from PROMPT_EOF to GH_AW_PROMPT_EOF in the integration tests.
• Update extractLinesFromYAML() parsing logic to detect the GH_AW_PROMPT_EOF delimiter.

Comments suppressed due to low confidence (2)

pkg/workflow/sh_integration_test.go:52

• These assertions hardcode the heredoc delimiter string in several places. To keep tests aligned with production behavior (and avoid future delimiter renames breaking tests), derive the delimiter via GenerateHeredocDelimiter("PROMPT") once and build the expected heredoc open/close markers from that value.

	heredocCount := strings.Count(result, `cat << 'GH_AW_PROMPT_EOF' >> "$GH_AW_PROMPT"`)
	if heredocCount < 2 {
		t.Errorf("Expected multiple heredoc blocks for large text (%d bytes), got %d", totalSize, heredocCount)
	}

	// Verify we didn't exceed 5 chunks
	if heredocCount > 5 {
		t.Errorf("Expected at most 5 heredoc blocks (max limit), got %d", heredocCount)
	}

	// Verify each heredoc is closed
	eofCount := strings.Count(result, indent+"GH_AW_PROMPT_EOF")
	if eofCount != heredocCount {

pkg/workflow/sh_integration_test.go:208

• extractLinesFromYAML duplicates the heredoc open/close strings again, which makes this helper easy to get out of sync with WritePromptTextToYAML. Consider passing the delimiter in (or computing it once inside the helper via GenerateHeredocDelimiter("PROMPT")) and matching based on that, rather than hardcoding GH_AW_PROMPT_EOF in multiple comparisons.

	for _, line := range strings.Split(yamlOutput, "\n") {
		// Check if we're starting a heredoc block
		if strings.Contains(line, `cat << 'GH_AW_PROMPT_EOF' >> "$GH_AW_PROMPT"`) {
			inHeredoc = true
			continue
		}

		// Check if we're ending a heredoc block
		if strings.TrimSpace(line) == "GH_AW_PROMPT_EOF" {
			inHeredoc = false

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

PR description says all tests were updated from PROMPT_EOF to GH_AW_PROMPT_EOF, but there are still PROMPT_EOF assertions in unit tests that exercise the same behavior (e.g., pkg/workflow/sh_test.go). Either update the remaining tests to use the generated delimiter or narrow/clarify the PR description so it matches the actual scope of the fix.

This issue also appears in the following locations of the same file:

• line 40
• line 199