Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Fix Step Name Alignment manifest path to avoid workspace access denials#33944

Merged
pelikhan merged 8 commits into
mainfrom
copilot/aw-step-name-alignment-fix
May 22, 2026
Merged

Fix Step Name Alignment manifest path to avoid workspace access denials#33944
pelikhan merged 8 commits into
mainfrom
copilot/aw-step-name-alignment-fix

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented May 22, 2026 •
edited
Loading

Step Name Alignment failed because the Claude agent was instructed to read its prebuilt manifest from /tmp/gh-aw/agent, which is outside the allowed working directory in this execution mode. The run then burned turns on blocked Bash attempts and terminated at max_turns.

  • Root-cause correction: manifest location

    • Move manifest generation from /tmp/gh-aw/agent/... to $GITHUB_WORKSPACE/.gh-aw/agent/... in the workflow source.
    • Keep generation logic unchanged; only pathing changes.

  • Prompt/runtime alignment

    • Update agent instructions in step-name-alignment.md to reference .gh-aw/agent/step-alignment-input.json (workspace-local path).
    • Regenerate step-name-alignment.lock.yml so compiled workflow behavior matches source.

  • Net effect

    • The agent now reads the prebuilt manifest from a path it is allowed to access, preventing the permission-denied loop that previously exhausted turn budget.
# before
MANIFEST_JSON="/tmp/gh-aw/agent/step-alignment-input.json"

# after
AGENT_INPUT_DIR="$GITHUB_WORKSPACE/.gh-aw/agent"
MANIFEST_JSON="$AGENT_INPUT_DIR/step-alignment-input.json"

Copilot AI linked an issue May 22, 2026 that may be closed by this pull request
[aw] Step Name Alignment failed #33936
Closed
Copilot AI changed the title [WIP] Fix step name alignment workflow failure Fix Step Name Alignment manifest path to avoid workspace access denials May 22, 2026
Copilot AI requested a review from pelikhan May 22, 2026 06:05
@github-actions github-actions Bot mentioned this pull request May 22, 2026
Closed
@pelikhan pelikhan marked this pull request as ready for review May 22, 2026 11:56
Copilot AI review requested due to automatic review settings May 22, 2026 11:56
Copilot AI reviewed May 22, 2026
View reviewed changes
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the Step Name Alignment workflow to generate/read its manifest from a workspace-local path (instead of /tmp/...) to avoid filesystem access denials in restricted execution modes, and regenerates the compiled lock workflow to match.

Changes:

  • Move manifest generation output from /tmp/gh-aw/agent/... to $GITHUB_WORKSPACE/.gh-aw/agent/... in Step Name Alignment.
  • Update Step Name Alignment agent instructions to reference .gh-aw/agent/step-alignment-input.json.
  • Regenerate workflow lock files (notably Step Name Alignment; DataFlow dataset lock file also changed substantially).
Show a summary per file
File Description
.github/workflows/step-name-alignment.md Writes manifest under workspace and updates prompt text to reference the new manifest path.
.github/workflows/step-name-alignment.lock.yml Compiled workflow updated to use the workspace-local manifest path and refreshed generated identifiers.
.github/workflows/dataflow-pr-discussion-dataset.lock.yml Regenerated compiled workflow with additional behavior/config changes beyond the PR’s stated scope.

Copilot's findings

Tip

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

Comments suppressed due to low confidence (1)

.github/workflows/dataflow-pr-discussion-dataset.lock.yml:117

  • The PR description focuses on Step Name Alignment, but this workflow is also changing core execution logic (e.g., adding a separate "Checkout actions folder" step and switching setup from a pinned action to a local ./actions/setup). If this is intentional, it should be called out explicitly; otherwise please revert/split these unrelated compiled-workflow changes to avoid accidental behavior changes.
      - name: Checkout actions folder
        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
        with:
          repository: github/gh-aw
          sparse-checkout: |
            actions
          persist-credentials: false
      - name: Setup Scripts
        id: setup
        uses: ./actions/setup
        with:
  • Files reviewed: 3/3 changed files
  • Comments generated: 1

Comment thread .github/workflows/dataflow-pr-discussion-dataset.lock.yml
Comment on lines 62 to 66
name: "DataFlow PR & Discussion Dataset Builder"
on:
schedule:
- cron: "25 7 * * 6"
- cron: "39 2 * * 5"
# Friendly format: weekly (scattered)
@pelikhan
Copy link
Copy Markdown
Collaborator

pelikhan commented May 22, 2026

@copilot this folder /tmp/gh-aw/agent should be always available for writing . Review agentic engine configurations and ensure it is configured to allow writes

Copy link
Copy Markdown
Contributor Author

Copilot AI commented May 22, 2026

@copilot this folder /tmp/gh-aw/agent should be always available for writing . Review agentic engine configurations and ensure it is configured to allow writes

Addressed in 36550dd (plus follow-up bd5edbd). I switched Step Name Alignment back to /tmp/gh-aw/agent and added sandbox filesystem config to explicitly allow writes to /tmp/gh-aw/agent, then regenerated the lock workflow so runtime permissions and compiled behavior stay aligned.

@pelikhan
Copy link
Copy Markdown
Collaborator

pelikhan commented May 22, 2026

@copilot this folder should always be writable for any agent and all workflows

Copy link
Copy Markdown
Contributor Author

Copilot AI commented May 22, 2026

@copilot this folder should always be writable for any agent and all workflows

Implemented globally in 826bfb7 (with follow-up test hardening in 3e4af2f and b21117f). Sandbox defaults now always inject /tmp/gh-aw/agent into sandbox.agent.config.filesystem.allowWrite for non-disabled agent sandboxes, so this path is writable across workflows and agent engines by default.

@pelikhan pelikhan merged commit 85c5828 into main May 22, 2026
@pelikhan pelikhan deleted the copilot/aw-step-name-alignment-fix branch May 22, 2026 12:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

Copilot code review Copilot Copilot left review comments

@pelikhan pelikhan Awaiting requested review from pelikhan

Assignees

@pelikhan pelikhan

Copilot code review Copilot

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

[aw] Step Name Alignment failed

3 participants

@pelikhan