Description

The push-to-pull-request-branch safe output compiles to max: 0 when max is not explicitly set in the frontmatter, effectively disabling it. The documentation states the default should be max: 1.

Expected Behavior

Per the Safe Outputs documentation:

Push to PR Branch (push-to-pull-request-branch) - Push changes to PR branch (default max: 1, configurable, same-repo only)

Omitting max should default to 1.

Actual Behavior

When max is omitted from the frontmatter:

safe-outputs:
  push-to-pull-request-branch:
    if-no-changes: ignore

The compiled lock file contains max: 0:

{"push_to_pull_request_branch":{"max":0}}

This causes the agent to succeed but report a no-op:

Documentation updated for PR #210 but push is disabled in this environment (push_to_pull_request_branch max: 0).

Workaround

Explicitly setting max: 1 in the frontmatter produces the correct lock file:

safe-outputs:
  push-to-pull-request-branch:
    max: 1
    if-no-changes: ignore

Compiled output:

{"push_to_pull_request_branch":{"max":1}}

Environment

• gh aw version: v0.53.3
• Workflow engine: default (Copilot)