Skip to content

Suggested test: copilot/post-steps-reject-direct-issue-creation #20624

Description

@github-actions

Motivation

Link to the gh-aw PR: github/gh-aw#66064 — Reject direct issue creation and safe-output access in post-steps

Proposed test

  • Workflow file: test-copilot-post-steps-direct-issue-rejection.md
  • Trigger: workflow_dispatch
  • Engine: copilot
  • Safe output: none expected to compile successfully — this is a negative compile test
  • Variant: standard

Minimal test prompt sketch

Add a steps: (post-step) entry that calls gh issue create directly, bypassing safe-outputs.create-issue. Compilation should fail with an error directing the author to use safe-outputs.create-issue.

New fixtures or secrets needed

None.

Notes

The current harness (e2e.sh) treats any workflow that fails to compile as an automatic test FAILURE (COMPILE_FAILED_FILE path), with no mechanism to assert "expected to fail to compile." Before writing this test, the harness would need a convention (e.g. a test-*-compile-failure naming pattern or marker file) to treat an expected compile error as a PASS. Flagging this as an open question for triage rather than submitting a PR directly.

Generated by 🔍 Suggest New E2E Tests · copilot · auto · 89.7 AIC · ⌖ 6.55 AIC · ⊞ 8.6K · ◷

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions