Something is confused in the usage model of --safe-update and --strict
If no flags are given for gh aw compile I get messages like
Remediation options:
1. Use an interactive agentic flow (e.g. Copilot CLI) to review and approve the changes.
2. Remove the --safe-update flag to allow the change.
3. Revert the unapproved changes from your workflow if they were added unintentionally.
This is because if no flags are given --strict is assumed, and --strict seems to imply --safe-update.
I don't understand what I as a user am meant to do in to allow the change. Adding --safe-update doesn't help and adding --strict doesn't help.
Since --safe-update is pretty much the default now (because strict is the default) I recommend we change --safe-update to --approve which approves any updates.
Something is confused in the usage model of --safe-update and --strict
If no flags are given for gh aw compile I get messages like
Remediation options:
1. Use an interactive agentic flow (e.g. Copilot CLI) to review and approve the changes.
2. Remove the --safe-update flag to allow the change.
3. Revert the unapproved changes from your workflow if they were added unintentionally.
This is because if no flags are given --strict is assumed, and --strict seems to imply --safe-update.
I don't understand what I as a user am meant to do in to allow the change. Adding --safe-update doesn't help and adding --strict doesn't help.
Since --safe-update is pretty much the default now (because strict is the default) I recommend we change --safe-update to --approve which approves any updates.