Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions pkg/workflow/strict_mode_test.go
Original file line number Diff line number Diff line change
Expand Up @@ -391,7 +391,7 @@ engine: copilot
tools:
github:
allowed: [issue_read]
bash:
bash: []
---

# Test Workflow`,
Expand Down Expand Up @@ -463,7 +463,7 @@ permissions:
timeout-minutes: 10
engine: copilot
tools:
bash:
bash: []
network:
allowed:
Comment on lines 464 to 468
Copy link

Copilot AI Feb 7, 2026

Choose a reason for hiding this comment

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

In this test case, the name says "bash null allowed in strict mode", but the YAML now uses bash: [] (empty list) and is identical to the next test case ("bash empty array allowed..."). This means the suite no longer covers the bash: null / anonymous bash: scenario, which is expected to be invalid per validateBashToolConfig. Consider either renaming/removing this case, or changing it to explicitly test bash: null and assert an error.

Copilot uses AI. Check for mistakes.
- "api.example.com"
Expand Down
Loading