Migrate workflows to GitHub Agentic Workflow (gh-aw) format by zircote · Pull Request #9 · zircote/nsip-example

zircote · 2026-02-20T09:41:05Z

Summary

Migrates 4 GitHub Actions workflows from YAML to gh-aw markdown format, consolidating trigger config and agent instructions into single files
Compiles all workflows to .lock.yml via gh aw compile for production use
Keeps copilot-setup-steps.yml (infrastructure) and dependabot-automerge.yml (CI reusable workflow) as standard YAML

Migrated Workflows

Workflow	Trigger	What it does
`flock-action.md`	Issue opened with `flock-action` label	Parses NSIP breeding analysis requests, calls MCP tools, produces report PR
`eov-enrichment.md`	Issue opened with `record:eov-*` or `eov-action` label	Enriches ecological monitoring records with trend data and EHI scores
`weekly-reminder.md`	Monday 8 AM UTC schedule	Creates weekly farm checklist issue
`eov-seasonal-reminder.md`	Quarterly schedule (Mar/Jun/Sep/Dec 1)	Creates seasonal ecological monitoring reminder with site checklist

Security Improvements

Read-only permissions in frontmatter; all writes gated through safe-outputs
Restricted bash allowlists (specific commands only, no unrestricted shell)
lock-for-agent: true prevents concurrent issue processing
Duplicate detection for scheduled workflows

Deleted Files

flock-action.yml (replaced by flock-action.md + .lock.yml)
eov-enrichment.yml (replaced by eov-enrichment.md + .lock.yml)
weekly-reminder.yml (replaced by weekly-reminder.md + .lock.yml)
eov-seasonal-reminder.yml (replaced by eov-seasonal-reminder.md + .lock.yml)

Test plan

Verify gh aw compile succeeds with 0 errors
Open a test issue with flock-action label and confirm agent processes it
Open a test issue with record:eov-site-assessment label and confirm enrichment
Trigger weekly-reminder via workflow_dispatch and confirm issue creation
Trigger eov-seasonal-reminder via workflow_dispatch and confirm issue creation
Confirm copilot-setup-steps.yml and dependabot-automerge.yml still function

🤖 Generated with Claude Code

Replace YAML workflows that assigned copilot-swe-agent or used github-script with unified gh-aw markdown files that combine trigger configuration and agent instructions in a single file. Migrated workflows: - flock-action: NSIP breeding analysis (consolidates .yml + instructions) - eov-enrichment: EOV ecological monitoring (consolidates .yml + instructions) - weekly-reminder: Monday farm checklist creation - eov-seasonal-reminder: Quarterly ecological monitoring reminder Kept as YAML (not agentic): - copilot-setup-steps.yml (infrastructure setup) - dependabot-automerge.yml (CI reusable workflow) Key improvements in gh-aw format: - Read-only permissions with writes gated through safe-outputs - Reaction feedback (eyes) on event-triggered workflows - Restricted bash allowlists (least-privilege) - Lock-for-agent to prevent concurrent processing - Duplicate detection for scheduled workflows - Edge case handling for invalid inputs - Branch-prefix constraints on PR creation

- Remove unsupported `reaction` and `branch-prefix` fields - Fix bash tool syntax (array format, not object) - Remove unsupported `max`/`discussions` on safe-outputs - Add compiled .lock.yml for all 4 agentic workflows - Add .gitattributes and .github/aw/ from gh-aw compiler

Copilot

Pull request overview

Migrates key farm automation workflows from traditional GitHub Actions YAML into GitHub Agentic Workflow (gh-aw) markdown sources, with compiled .lock.yml workflows intended for production execution.

Changes:

Replaced 4 legacy workflows with gh-aw .md workflow definitions plus generated .lock.yml files.
Added gh-aw action pin manifest (.github/aw/actions-lock.json) and marked compiled workflows as generated via .gitattributes.

Reviewed changes

Copilot reviewed 14 out of 14 changed files in this pull request and generated 7 comments.

Show a summary per file

File	Description
.github/workflows/weekly-reminder.yml	Deleted legacy scheduled issue-creation workflow (replaced by gh-aw).
.github/workflows/weekly-reminder.md	New gh-aw source defining weekly checklist issue creation.
.github/workflows/weekly-reminder.lock.yml	Generated compiled workflow for production execution of weekly reminder.
.github/workflows/flock-action.yml	Deleted legacy “assign agent on label” workflow (replaced by gh-aw).
.github/workflows/flock-action.md	New gh-aw source for NSIP flock-action issue processing and report PR creation.
.github/workflows/flock-action.lock.yml	Generated compiled workflow for production execution of flock-action.
.github/workflows/eov-seasonal-reminder.yml	Deleted legacy quarterly reminder workflow (replaced by gh-aw).
.github/workflows/eov-seasonal-reminder.md	New gh-aw source defining quarterly EOV monitoring reminder issue creation.
.github/workflows/eov-seasonal-reminder.lock.yml	Generated compiled workflow for production execution of seasonal reminder.
.github/workflows/eov-enrichment.yml	Deleted legacy “assign agent on label” workflow (replaced by gh-aw).
.github/workflows/eov-enrichment.md	New gh-aw source for EOV record enrichment + EOV action report generation.
.github/workflows/eov-enrichment.lock.yml	Generated compiled workflow for production execution of EOV enrichment/actions.
.github/aw/actions-lock.json	Adds pinned SHAs for gh-aw referenced actions.
.gitattributes	Marks `.lock.yml` workflows as generated and sets merge strategy.

Copilot · 2026-02-20T09:47:13Z

.github/workflows/weekly-reminder.md

+safe-outputs:
+  create-issue:
+    title-prefix: "Weekly Farm Check - "
+    labels: [routine, maintenance]
+    max: 1


The safe-outputs config applies a "Weekly Farm Check - " title prefix, but the instructions below also tell the agent to create a title that already starts with "Weekly Farm Check -". This will likely produce duplicated prefixes in created issues. Align this by either removing the title-prefix or updating the instructions so the agent provides only the suffix (e.g., "Week {N}").

Copilot · 2026-02-20T09:47:13Z

.github/workflows/eov-seasonal-reminder.md

+
+safe-outputs:
+  create-issue:
+    title-prefix: "EOV "


The safe-outputs config prefixes titles with "EOV ", but the instructions also specify creating a title that already starts with "EOV" ("EOV {Season} {Year} Monitoring"). This will likely result in duplicated "EOV" prefixes on created issues. Consider removing the title-prefix or adjusting the instructed title to omit the leading "EOV".

Suggested change

title-prefix: "EOV "

Copilot · 2026-02-20T09:47:13Z

.github/workflows/flock-action.md

+  create-pull-request:
+    title-prefix: "[Flock Action] "


safe-outputs.create-pull-request adds a "[Flock Action] " title prefix, but later instructions also tell the agent to create a PR title that already starts with "[Flock Action]". This can lead to duplicated prefixes in PR titles. Align by removing the prefix or adjusting the instructed title to omit it.

Suggested change

create-pull-request:

title-prefix: "[Flock Action] "

create-pull-request: {}

Copilot · 2026-02-20T09:47:14Z

.github/workflows/weekly-reminder.lock.yml

+        run: |
+          set -o pipefail
+          sudo -E awf --env-all --container-workdir "${GITHUB_WORKSPACE}" --allow-domains api.business.githubcopilot.com,api.enterprise.githubcopilot.com,api.github.com,api.githubcopilot.com,api.individual.githubcopilot.com,api.snapcraft.io,archive.ubuntu.com,azure.archive.ubuntu.com,crl.geotrust.com,crl.globalsign.com,crl.identrust.com,crl.sectigo.com,crl.thawte.com,crl.usertrust.com,crl.verisign.com,crl3.digicert.com,crl4.digicert.com,crls.ssl.com,github.com,host.docker.internal,json-schema.org,json.schemastore.org,keyserver.ubuntu.com,ocsp.digicert.com,ocsp.geotrust.com,ocsp.globalsign.com,ocsp.identrust.com,ocsp.sectigo.com,ocsp.ssl.com,ocsp.thawte.com,ocsp.usertrust.com,ocsp.verisign.com,packagecloud.io,packages.cloud.google.com,packages.microsoft.com,ppa.launchpad.net,raw.githubusercontent.com,registry.npmjs.org,s.symcb.com,s.symcd.com,security.ubuntu.com,telemetry.enterprise.githubcopilot.com,ts-crl.ws.symantec.com,ts-ocsp.ws.symantec.com --log-level info --proxy-logs-dir /tmp/gh-aw/sandbox/firewall/logs --enable-host-access --image-tag 0.20.2 --skip-pull --enable-api-proxy \
+            -- /bin/bash -c '/usr/local/bin/copilot --add-dir /tmp/gh-aw/ --log-level all --log-dir /tmp/gh-aw/sandbox/agent/logs/ --add-dir "${GITHUB_WORKSPACE}" --disable-builtin-mcps --allow-all-tools --allow-all-paths --share /tmp/gh-aw/sandbox/agent/logs/conversation.md --prompt "$(cat /tmp/gh-aw/aw-prompts/prompt.txt)"${GH_AW_MODEL_AGENT_COPILOT:+ --model "$GH_AW_MODEL_AGENT_COPILOT"}' 2>&1 | tee -a /tmp/gh-aw/agent-stdio.log


This workflow executes Copilot with "--allow-all-tools" and "--allow-all-paths", which effectively removes the intended tool and filesystem restrictions and undermines the PR’s stated security posture. Update the generated workflow so the agent run uses an explicit allowlist (similar to the other gh-aw compiled workflows) and avoids allow-all-tools/paths.

Suggested change

-- /bin/bash -c '/usr/local/bin/copilot --add-dir /tmp/gh-aw/ --log-level all --log-dir /tmp/gh-aw/sandbox/agent/logs/ --add-dir "${GITHUB_WORKSPACE}" --disable-builtin-mcps --allow-all-tools --allow-all-paths --share /tmp/gh-aw/sandbox/agent/logs/conversation.md --prompt "$(cat /tmp/gh-aw/aw-prompts/prompt.txt)"${GH_AW_MODEL_AGENT_COPILOT:+ --model "$GH_AW_MODEL_AGENT_COPILOT"}' 2>&1 | tee -a /tmp/gh-aw/agent-stdio.log

-- /bin/bash -c '/usr/local/bin/copilot --add-dir /tmp/gh-aw/ --log-level all --log-dir /tmp/gh-aw/sandbox/agent/logs/ --add-dir "${GITHUB_WORKSPACE}" --allow-path /tmp/gh-aw/ --allow-path "${GITHUB_WORKSPACE}" --disable-builtin-mcps --share /tmp/gh-aw/sandbox/agent/logs/conversation.md --prompt "$(cat /tmp/gh-aw/aw-prompts/prompt.txt)"${GH_AW_MODEL_AGENT_COPILOT:+ --model "$GH_AW_MODEL_AGENT_COPILOT"}' 2>&1 | tee -a /tmp/gh-aw/agent-stdio.log

Copilot · 2026-02-20T09:47:14Z

.github/workflows/flock-action.lock.yml

+name: "Flock Action Workflow"
+"on":
+  issues:
+    # lock-for-agent: true # Lock-for-agent processed as issue locking in activation job
+    # names: # Label filtering applied via job conditions
+    # - flock-action # Label filtering applied via job conditions
+    types:
+    - opened
+


The compiled workflow triggers on every newly opened issue ("on: issues: opened") and does not contain any job-level condition that checks for the "flock-action" label. As a result, it can run (and lock issues / spend agent minutes) for unrelated issues opened by repo members. Add an explicit label gate (like the previous YAML’s contains(label) check) so the workflow only activates for issues labeled "flock-action".

Copilot · 2026-02-20T09:47:14Z

.github/workflows/eov-enrichment.lock.yml

+name: "EOV Enrichment Workflow"
+"on":
+  issues:
+    # lock-for-agent: true # Lock-for-agent processed as issue locking in activation job
+    # names: # Label filtering applied via job conditions
+    # - record:eov-site-assessment # Label filtering applied via job conditions
+    # - record:eov-soil-sample # Label filtering applied via job conditions
+    # - record:eov-water-test # Label filtering applied via job conditions
+    # - record:eov-photo-point # Label filtering applied via job conditions
+    # - eov-action # Label filtering applied via job conditions
+    types:
+    - opened


The compiled workflow triggers on every newly opened issue and does not include a job-level condition to ensure one of the intended EOV labels is present. This means the workflow may run (and lock issues / spend agent minutes) for unrelated issues opened by repo members. Add an explicit label gate (equivalent to the prior YAML contains(label) checks) so it only activates for EOV record/action issues.

Copilot · 2026-02-20T09:47:15Z

.github/workflows/flock-action.md

+mcp-servers:
+  nsip:
+    command: "docker"
+    args: ["run", "--rm", "-i", "ghcr.io/zircote/nsip", "mcp"]


This workflow invokes docker run ghcr.io/zircote/nsip mcp via an MCP server definition using a mutable image reference, which creates a supply chain risk. If the ghcr.io/zircote/nsip image or registry is compromised, an attacker could run arbitrary code in your workflow with access to the repository checkout and any tokens/permissions granted, allowing data exfiltration or tampering with generated reports. To mitigate this, pin the image to an immutable digest (for example using an @sha256:... reference) and ensure the container runs with the minimum necessary permissions and network access.

zircote · 2026-02-20T09:51:38Z

@copilot open a new pull request to apply changes based on the comments in this thread

Copilot · 2026-02-20T09:51:46Z

@zircote I've opened a new pull request, #10, to work on those changes. Once the pull request is ready, I'll request review from you.

zircote · 2026-02-21T02:39:31Z

@copilot open a new pull request to apply changes based on the comments in this thread

Copilot · 2026-02-21T02:39:39Z

@zircote I've opened a new pull request, #11, to work on those changes. Once the pull request is ready, I'll request review from you.

… digest pinning (#11) * Initial plan * Fix review comments: label gates, title prefix duplication, security improvements Co-authored-by: zircote <307960+zircote@users.noreply.github.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: zircote <307960+zircote@users.noreply.github.com>

…urity restrictions, and Docker image pinning (#10) * Initial plan * Address review comments: fix duplicate title prefixes, label gates, security restrictions, and Docker image pinning Co-authored-by: zircote <307960+zircote@users.noreply.github.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: zircote <307960+zircote@users.noreply.github.com> Co-authored-by: Robert Allen <zircote@gmail.com>

zircote added 2 commits February 20, 2026 04:34

Copilot AI review requested due to automatic review settings February 20, 2026 09:41

Copilot started reviewing on behalf of zircote February 20, 2026 09:41 View session

Copilot AI reviewed Feb 20, 2026

View reviewed changes

Copilot AI mentioned this pull request Feb 20, 2026

Fix gh-aw workflow issues: label gates, duplicate title prefixes, security restrictions, and Docker image pinning #10

Merged

Copilot AI mentioned this pull request Feb 21, 2026

Fix label gates, duplicate title prefixes, allow-all-tools, and image digest pinning #11

Merged

Copilot AI and others added 2 commits February 20, 2026 22:49

zircote merged commit f42b5eb into main Feb 21, 2026
1 check passed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Migrate workflows to GitHub Agentic Workflow (gh-aw) format#9

Migrate workflows to GitHub Agentic Workflow (gh-aw) format#9
zircote merged 4 commits intomainfrom
feature/gh-aw-migration

zircote commented Feb 20, 2026

Uh oh!

Copilot AI left a comment

Uh oh!

Copilot AI Feb 20, 2026

Uh oh!

Copilot AI Feb 20, 2026

Uh oh!

Copilot AI Feb 20, 2026

Uh oh!

Copilot AI Feb 20, 2026

Uh oh!

Copilot AI Feb 20, 2026

Uh oh!

Copilot AI Feb 20, 2026

Uh oh!

Copilot AI Feb 20, 2026

Uh oh!

zircote commented Feb 20, 2026

Uh oh!

Copilot AI commented Feb 20, 2026

Uh oh!

zircote commented Feb 21, 2026

Uh oh!

Copilot AI commented Feb 21, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

	create-pull-request:
	title-prefix: "[Flock Action] "
	create-pull-request: {}

Conversation

zircote commented Feb 20, 2026

Summary

Migrated Workflows

Security Improvements

Deleted Files

Test plan

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Copilot AI Feb 20, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 20, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 20, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 20, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 20, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 20, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 20, 2026

Choose a reason for hiding this comment

Uh oh!

zircote commented Feb 20, 2026

Uh oh!

Copilot AI commented Feb 20, 2026

Uh oh!

zircote commented Feb 21, 2026

Uh oh!

Copilot AI commented Feb 21, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants