You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
No-op runs still reported after #4033 — gh-aw compiler bug (#4050)
PR #4033 correctly set `report-as-issue: false` in the `.md` source and
the compiled JSON config blobs picked it up. However, `gh aw compile`
hardcodes `GH_AW_NOOP_REPORT_AS_ISSUE: "true"` in the "Handle No-Op
Message" step env (line 1003 of the lock file) regardless of the
frontmatter setting. The `handle_noop_message.cjs` script reads this env
var, so no-op runs continued to be reported.
This is a bug in `gh-aw`'s compiler — the env var does not reflect the
`safe-outputs.noop.report-as-issue` config from the source `.md`. The
lock file should not be manually edited; this needs to be fixed upstream
in `gh-aw`.
<!-- START COPILOT CODING AGENT TIPS -->
---
💬 Send tasks to Copilot coding agent from
[Slack](https://gh.io/cca-slack-docs) and
[Teams](https://gh.io/cca-teams-docs) to turn conversations into code.
Copilot posts an update in your thread when it's finished.
---------
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: heaths <1532486+heaths@users.noreply.github.com>
Co-authored-by: Heath Stewart <heaths@microsoft.com>
@@ -92,7 +92,7 @@ When you interact with this agent, it will:
92
92
### Create a Report-Generating Workflow
93
93
**Load when**: The workflow being created or updated produces reports — recurring status updates, audit summaries, analyses, or any structured output posted as a GitHub issue, discussion, or comment
- "Create a shared component for Notion integration"
@@ -112,7 +112,7 @@ When you interact with this agent, it will:
112
112
### Fix Dependabot PRs
113
113
**Load when**: User needs to close or fix open Dependabot PRs that update dependencies in generated manifest files (`.github/workflows/package.json`, `.github/workflows/requirements.txt`, `.github/workflows/go.mod`)
- "Fix the open Dependabot PRs for npm dependencies"
@@ -122,7 +122,7 @@ When you interact with this agent, it will:
122
122
### Analyze Test Coverage
123
123
**Load when**: The workflow reads, analyzes, or reports test coverage — whether triggered by a PR, a schedule, or a slash command. Always consult this prompt before designing the coverage data strategy.
- "Create a workflow that comments coverage on PRs"
@@ -169,10 +169,10 @@ gh aw compile --validate
169
169
170
170
## Important Notes
171
171
172
-
- Always reference the instructions file at https://github.com/github/gh-aw/blob/v0.63.1/.github/aw/github-agentic-workflows.md for complete documentation
172
+
- Always reference the instructions file at https://github.com/github/gh-aw/blob/v0.64.1/.github/aw/github-agentic-workflows.md for complete documentation
173
173
- Use the MCP tool `agentic-workflows` when running in GitHub Copilot Cloud
174
174
- Workflows must be compiled to `.lock.yml` files before running in GitHub Actions
175
175
-**Bash tools are enabled by default** - Don't restrict bash commands unnecessarily since workflows are sandboxed by the AWF
176
176
- Follow security best practices: minimal permissions, explicit network access, no template injection
177
-
-**Network configuration**: Use ecosystem identifiers (`node`, `python`, `go`, etc.) or explicit FQDNs in `network.allowed`. Bare shorthands like `npm` or `pypi` are **not** valid. See https://github.com/github/gh-aw/blob/v0.63.1/.github/aw/network.md for the full list of valid ecosystem identifiers and domain patterns.
177
+
-**Network configuration**: Use ecosystem identifiers (`node`, `python`, `go`, etc.) or explicit FQDNs in `network.allowed`. Bare shorthands like `npm` or `pypi` are **not** valid. See https://github.com/github/gh-aw/blob/v0.64.1/.github/aw/network.md for the full list of valid ecosystem identifiers and domain patterns.
178
178
-**Single-file output**: When creating a workflow, produce exactly **one** workflow `.md` file. Do not create separate documentation files (architecture docs, runbooks, usage guides, etc.). If documentation is needed, add a brief `## Usage` section inside the workflow file itself.
0 commit comments