I made some changes to Safe outputs to try to make it less intrusive, so the compilation process inserts the prompting related to
For example see https://github.com/githubnext/gh-aw/blob/21577fc54bafa39597854e8dba494826e81d82da/.github/workflows/test-claude-add-issue-labels.lock.yml#L189C1-L194C1
For safe-outputs: --> add-issue-labels this gets inserted:
## Adding Labels to Issues or Pull Requests
To add labels to an issue or pull request on GitHub, do NOT attempt to use MCP tools, do NOT attempt to use `gh` and do NOT attempt to use the GitHub API. Instead, write the list of labels, one on each line, to "${{ env.GITHUB_AW_OUTPUT }}", where each line is a label.
The aim is to make it that the prompting doesn't need to know about GITHUB_AW_OUTPUT or its output at all, and that over tim we can change it to be whatever format and prompting is most reliable, and use it to add more possible outputs.
However this prompting may not be strong enough and we need to check that this actually works.
I made some changes to Safe outputs to try to make it less intrusive, so the compilation process inserts the prompting related to
For example see https://github.com/githubnext/gh-aw/blob/21577fc54bafa39597854e8dba494826e81d82da/.github/workflows/test-claude-add-issue-labels.lock.yml#L189C1-L194C1
For
safe-outputs:-->add-issue-labelsthis gets inserted:The aim is to make it that the prompting doesn't need to know about GITHUB_AW_OUTPUT or its output at all, and that over tim we can change it to be whatever format and prompting is most reliable, and use it to add more possible outputs.
However this prompting may not be strong enough and we need to check that this actually works.