Skip to content

[product-manager-impersonator] Single-workflow compile target #1063

Open

Description

@github-actions

Feature Idea

Summary: Add an optional targeted compile command (make compile-workflow WORKFLOW=<name>) so maintainers can regenerate only one workflow’s generated files during edits.

Why a Customer Would Want This

Workflow maintainers usually touch one workflow at a time, but today the documented path always recompiles and re-syncs the entire catalog. That makes iteration slower and creates large unrelated generated diffs, which is frustrating for contributors and reviewers.

Rough Implementation Sketch

  • Add a compile-workflow Make target that requires WORKFLOW=<name> and compiles only the matching workflow source/lock file.
  • Extend scripts/dogfood.sh with an optional workflow filter so sync can regenerate only trigger-<name>.yml (including existing dogfood override and remediation-chain behavior).
  • Keep make compile as the full-repo path; the new target is additive for focused edits.
  • Document the new command in gh-agent-workflows/DEVELOPING.md next to the current make compile guidance.

Why It Won't Be That Hard

This is a focused ergonomics improvement with a small implementation surface (Makefile target + optional filter in one script + docs). It reuses existing compile/sync logic rather than introducing a new build system path.

Evidence

Note

🔒 Integrity filter blocked 11 items

The following items were blocked because they don't meet the GitHub integrity level.

  • Issue Fixer can use Ephemeral Token #1025 list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #359 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #354 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #336 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #139 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #704 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #248 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #235 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #684 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #505 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #476 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

What is this? | From workflow: Trigger Product Manager Impersonator

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions