Add actions directory structure and Go-based build tooling for custom GitHub Actions by Copilot · Pull Request #5953 · github/gh-aw

Copilot · 2025-12-09T13:14:45Z

Plan: Create Actions Directory Structure and Build Tooling

Understanding

Create foundational structure for custom GitHub Actions to migrate from inline JavaScript
Focus on safe-inputs and safe-outputs MCP server actions initially
Establish build tooling to bundle, validate, and manage action packages
Implement Go-based build system that reuses workflow bundler infrastructure
Use internal development tool (not main CLI) for action management commands

Checklist

Summary

Successfully implemented the foundational directory structure and Go-based build tooling for custom GitHub Actions. The system reuses the workflow bundler and script registry infrastructure, providing a unified approach to JavaScript bundling across the project.

Key Features

✅ Clean, organized directory structure following GitHub Actions standards
✅ 100% Go-based build system - No JavaScript build scripts
✅ Internal development tool - Commands separated from main gh aw CLI
✅ Script registry integration for accessing embedded JavaScript sources
✅ Automated build tooling that embeds JavaScript dependencies
✅ Validation system for action.yml files
✅ Makefile interface - Primary way to invoke build commands
✅ Direct go run execution - No binary build required for development commands
✅ CI integration - Actions are built and validated in CI pipeline
✅ Comprehensive specification - Complete documentation in specs/actions.md
✅ Two initial actions ready for use: setup-safe-inputs and setup-safe-outputs
✅ Proper .gitignore configuration
✅ Generated files marked in .gitattributes
✅ Standard naming convention with "setup-" prefix following GitHub Actions best practices
✅ Merged with latest main branch changes

Build System Architecture

The build system consists of:

Internal Tool (internal/tools/actions-build/main.go): Lightweight CLI dispatcher for development commands
Build Logic (pkg/cli/actions_build_command.go): Pure Go implementation reusing workflow bundler infrastructure
Makefile Interface: Primary entry point (make actions-build, make actions-validate, make actions-clean)
CI Validation: Automated testing in GitHub Actions

Commands are not part of the main gh aw CLI (which is for end users), but are invoked through the Makefile which runs the internal tool at internal/tools/actions-build.

CI Integration

Added actions-build job to .github/workflows/ci.yml:

Depends on lint job
Builds all actions using make actions-build
Validates action.yml files using make actions-validate
Triggers on pull requests when actions/** files change
Ensures actions compile correctly before merging

Documentation

Updated specs/actions.md with accurate documentation:

Motivation: Problem statement and solution approach
Architecture: Component diagrams showing Makefile → internal tool → build logic flow
Directory Structure: Layouts and file organization
Build System: Pure Go implementation details with internal tool
Architectural Decisions: Rationale for key choices (reuse bundler, manual dependencies, commit bundled files, use go run, Node.js 20, internal tool)
Usage Guide: Creating and using actions with Makefile examples only
CI Integration: Validation pipeline documentation
Development Guide: Quick start emphasizing internal tool architecture
Future Work: Enhancement roadmap and migration path

Key clarifications:

Build system is 100% Go code (no JavaScript build scripts)
Commands are in internal tool (internal/tools/actions-build), not main CLI
Primary interface is Makefile (make actions-build, etc.)

Next Steps (Future Work)

Implement automatic dependency resolution using Go functions
Add more actions as needed for workflow compilation
Migrate existing inline scripts to custom actions
Add action versioning and distribution support

Original prompt

This section details on the original issue you should resolve

<issue_title>[plan] Create actions directory structure and build tooling</issue_title>
<issue_description>## Objective

Set up the foundational directory structure and build tooling to support custom GitHub Actions for JavaScript modules.

Context

This is the first step in migrating from inline JavaScript to custom actions. We need a clean directory structure and automation to manage multiple action packages.

Tasks
Create actions/ directory at repository root

Design directory structure (e.g., actions/{action-name}/)

Add Makefile targets for action management:

make actions-build - Bundle all action JavaScript

make actions-validate - Validate action.yml files

make actions-clean - Clean generated files
Create a template structure for new actions:
actions/{action-name}/
├── action.yml
├── index.js (bundled)
├── src/ (source files if needed)
└── README.md
Update .gitignore to exclude temporary build artifacts (but include bundled index.js)
Files to Create/Modify

Create: actions/ directory

Update: Makefile (add action-related targets)

Update: .gitignore (if needed)

Create: scripts/build-actions.js (or similar tooling script)

Acceptance Criteria

actions/ directory exists with clear structure

Makefile has targets for building and validating actions

Documentation explains the action directory structure

Build tooling can validate action.yml format

Structure supports both simple (single-file) and complex (multi-file) actions
Related to [plan] Refactor compiler to use custom actions for JavaScript code #5947

AI generated by Plan Command for #5946

Comments on the Issue (you are @copilot in this section)
@pelikhan For the safe inputs, safe outputs MCP server, create actions that copy the files locally. @pelikhan Create plan to migrate from using GitHub script APIs to custom action

Fixes [plan] Create actions directory structure and build tooling #5948

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

Changeset

Type: patch
Description: Add actions directory structure and Go-based build tooling; initial actions and Makefile targets (setup-safe-inputs and setup-safe-outputs). Fixes [plan] Create actions directory structure and build tooling #5948

Ahoy! This treasure was crafted by 🏴‍☠️ Changeset Generator

pelikhan · 2025-12-09T13:17:51Z

@copilot update .gitattributes to mark compiler generated files

Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>

- Created actions/ directory with subdirectories for safe-inputs-copy and safe-outputs-copy - Added action.yml files for both actions with proper metadata - Created source JavaScript files in src/ directories - Implemented build-actions.js script for bundling, validation, and cleaning - Added Makefile targets: actions-build, actions-validate, actions-clean - Updated .gitignore to include bundled index.js but exclude temp artifacts - Added comprehensive documentation in actions/README.md - Successfully built and validated both initial actions Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>

- Clarified TODO about automatic dependency resolution - Added note about manual dependency mapping maintenance - Recompiled workflow lock files after build Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>

Added actions/*/index.js pattern to mark bundled action files as linguist-generated Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>

Copilot · 2025-12-09T13:42:59Z

@copilot update .gitattributes to mark compiler generated files

Updated .gitattributes to mark actions/*/index.js files as linguist-generated=true. This ensures the bundled action files are properly marked as compiler-generated code while source files in src/ directories remain unmarked. (3caba7d)

pelikhan · 2025-12-09T14:17:00Z

@copilot names should be "safe-inputs", "safe-outputs".

…/safe-outputs - Renamed action directories to use hyphenated names without -copy suffix - Updated all documentation references in README files - Updated build-actions.js dependency mapping - Updated action.yml names to "Safe Inputs" and "Safe Outputs" - Rebuilt and validated actions with new names Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>

Copilot · 2025-12-09T14:25:17Z

@copilot names should be "safe-inputs", "safe-outputs".

Renamed actions to safe-inputs and safe-outputs (without -copy suffix). Updated all references in documentation, build scripts, and action.yml files. (5ef0b0a)

pelikhan · 2025-12-09T14:27:15Z

@copilot rename safe-inputs, safe-outputs to setup-safe-inputs, setup-safe-outputs

- Renamed action directories from safe-inputs/safe-outputs to setup-safe-inputs/setup-safe-outputs - Updated all documentation references in README files - Updated build-actions.js dependency mapping - Updated action.yml names to "Setup Safe Inputs" and "Setup Safe Outputs" - Rebuilt and validated actions with new names Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>

Copilot · 2025-12-09T14:34:18Z

@copilot rename safe-inputs, safe-outputs to setup-safe-inputs, setup-safe-outputs

Renamed actions to setup-safe-inputs and setup-safe-outputs. Updated all references in documentation, build scripts, and action.yml files. (c1f6eb5)

pelikhan · 2025-12-09T16:08:38Z

@copilot merge main

…s-directory-structure # Please enter a commit message to explain why this merge is necessary, # especially if it merges an updated upstream into a topic branch. # # Lines starting with '#' will be ignored, and an empty message aborts # the commit.

Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>

Copilot · 2025-12-09T16:16:18Z

@copilot merge main

Merged main branch successfully. Recompiled workflows and pushed changes. (6ca9a2c, 70622a7)

Copilot · 2025-12-09T17:51:28Z

@copilot generate a specs/actions.md file with a summary of the work done so far, the architectural decisions, and a mini-dev guide for the next agent.

Created specs/actions.md with comprehensive documentation covering:

Architecture & Decisions:

Component diagram showing how CLI, build system, and workflow infrastructure interact
5 key architectural decisions with rationale (reuse bundler, manual dependencies, commit bundled files, use go run, Node.js 20)

Implementation Details:

Directory structure and file layouts
Build process flow (discovery → validation → bundling → output)
Source file patterns with FILES placeholder
Dependency mapping approach

Developer Guide:

Quick start for future agents
Common tasks (add action, update dependencies, add JS source)
Key files to know
Debugging tips
Future enhancement roadmap

The spec provides a complete reference for understanding and extending the custom actions build system. (ce1f051)

pelikhan · 2025-12-09T18:03:17Z

+
+```bash
+# Build all actions
+gh aw actions-build


@copilot remove gh aw actions-build reference, and only use make commands

Removed all gh aw actions-build CLI references from specs/actions.md. The document now only shows Makefile commands (make actions-build, etc.) as the primary interface. (933ec75)

pelikhan · 2025-12-09T18:03:54Z

@copilot this document looks outdated. Look at the current changes and update. The build process is now all in go.

Updated specs/actions.md to accurately reflect the current Go-based implementation:

Added prominent notes that build system is 100% Go code (no JavaScript build scripts)

Updated architecture diagram to show Makefile → go run flow

Clarified component responsibilities with Makefile as entry point

Emphasized throughout that there are no JavaScript build scripts (no scripts/build-actions.js)

Updated key files section to highlight pure Go implementation in pkg/cli/actions_build_command.go

The spec now correctly documents that all build logic is in Go and reuses the workflow compiler's bundler infrastructure. (933ec75)

github-actions · 2025-12-09T18:05:52Z

📰 DEVELOPING STORY: Smoke Copilot Playwright reports failed. Our correspondents are investigating the incident...

github-actions · 2025-12-09T18:05:52Z

🔮 The ancient spirits stir... Smoke Codex awakens to divine this pull request...

github-actions · 2025-12-09T18:05:53Z

💥 WHOOSH! Smoke Claude springs into action on this pull request! [Panel 1 begins...]

github-actions · 2025-12-09T18:05:53Z

⚠️ Security scanning failed for Smoke Copilot Safe Inputs. Review the logs for details.

github-actions · 2025-12-09T18:05:54Z

⚠️ Security scanning failed for Smoke Copilot. Review the logs for details.

github-actions · 2025-12-09T18:05:55Z

🎉 Yo ho ho! Changeset Generator found the treasure and completed successfully! ⚓💰

https://github.com/githubnext/gh-aw/tree/copilot/create-actions-directory-structure

github-actions · 2025-12-09T18:08:31Z

Smoke Test Results

Last 2 Merged PRs:

[WIP] Format code, lint and fix failing tests #5974: [WIP] Format code, lint and fix failing tests
Add ci-cleaner custom agent for automating repository CI maintenance #5975: Add ci-cleaner custom agent for automating repository CI maintenance

Test Results:

✅ GitHub MCP: Retrieved PR list
✅ File Writing: Created test file successfully
✅ Bash Tool: Verified file contents
✅ Playwright MCP: Navigated to GitHub, title contains "GitHub"
✅ Cache Memory: Created and verified cache file

Status: PASS

💥 [THE END] — Illustrated by Smoke Claude fer issue #5953 🗺️

github-actions · 2025-12-09T18:10:02Z

Recent merged PRs: [WIP] Format code, lint and fix failing tests; Add ci-cleaner custom agent for automating repository CI maintenance
GitHub MCP PR fetch: ✅
Agent file write/read: ✅
Playwright title check: ✅
Cache memory write/read: ✅
safeinputs-gh issues list: ❌ (tool unavailable here)
Overall: FAIL

🔮 The oracle has spoken through Smoke Codex fer issue #5953 🗺️

…sage Changes: - Removed all CLI command references (gh aw actions-*) - Updated to only show Makefile commands (make actions-build, etc.) - Added prominent notes that build system is 100% Go (no JavaScript build scripts) - Updated architecture diagram to show Makefile → go run flow - Clarified component responsibilities with Makefile as entry point - Emphasized throughout that there are no JavaScript build scripts - Updated key files section to highlight pure Go implementation The spec now accurately reflects that the build system is entirely Go-based and invoked via Makefile for development. Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>

github-actions · 2025-12-09T18:10:32Z

Smoke Test Results

PRs: #5974 (Format code, lint and fix failing tests), #5975 (Add ci-cleaner custom agent)

✅ GitHub MCP: Read merged PRs
✅ File Writing: Created test file
✅ Bash Tools: Verified file contents
✅ GitHub MCP Default Toolset: get_me correctly unavailable (403)
✅ Cache Memory: Created and verified cache file
✅ Available Tools: github-, safeoutputs-, create-, debug-, etc.

Status: PASS

📰 BREAKING: Report filed by Smoke Copilot fer issue #5953 🗺️

pelikhan · 2025-12-09T18:39:15Z

@copilot move the new command out of the cli into an internal tool

Moved actions-build, actions-validate, and actions-clean commands out of the main gh-aw CLI into an internal development tool: - Created internal/tools/actions-build/main.go as lightweight CLI dispatcher - Removed action commands from cmd/gh-aw/main.go (no longer in end-user CLI) - Updated Makefile to invoke internal tool: go run ./internal/tools/actions-build - Updated specs/actions.md to document internal tool architecture - Commands remain available via Makefile: make actions-build, etc. These are development-only commands not intended for end users, so they belong in an internal tool rather than the main CLI. Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>

Copilot · 2025-12-09T18:48:47Z

@copilot move the new command out of the cli into an internal tool

Moved actions commands out of the main gh aw CLI into an internal development tool:

Created: internal/tools/actions-build/main.go - Lightweight CLI dispatcher for development-only commands
Removed: Commands from cmd/gh-aw/main.go (no longer in end-user CLI)
Updated: Makefile now invokes go run ./internal/tools/actions-build <command>
Updated: specs/actions.md to document the internal tool architecture

Commands remain accessible via Makefile (make actions-build, etc.) but are no longer part of the main CLI since they're development-only tools. (2c55703)

… GitHub Actions Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>

Initial plan

4bf6cb9

Copilot AI assigned Copilot and pelikhan Dec 9, 2025

Copilot started work on behalf of pelikhan December 9, 2025 13:15 View session

Copilot AI and others added 3 commits December 9, 2025 13:19

Initial plan for actions directory structure and build tooling

03e3a3b

Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>

Update TODO comment in build-actions.js for clarity

a84c0eb

- Clarified TODO about automatic dependency resolution - Added note about manual dependency mapping maintenance - Recompiled workflow lock files after build Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>

Copilot AI changed the title ~~[WIP] Set up actions directory structure and build tooling~~ Add actions directory structure and build tooling for custom GitHub Actions Dec 9, 2025

Copilot AI requested a review from pelikhan December 9, 2025 13:37

Copilot finished work on behalf of pelikhan December 9, 2025 13:37

Copilot started work on behalf of pelikhan December 9, 2025 13:39 View session

Mark compiler generated action index.js files in .gitattributes

3caba7d

Added actions/*/index.js pattern to mark bundled action files as linguist-generated Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>

Copilot finished work on behalf of pelikhan December 9, 2025 13:44

Copilot started work on behalf of pelikhan December 9, 2025 14:17 View session

Copilot finished work on behalf of pelikhan December 9, 2025 14:27

Copilot started work on behalf of pelikhan December 9, 2025 14:27 View session

Copilot finished work on behalf of pelikhan December 9, 2025 14:36

Copilot started work on behalf of pelikhan December 9, 2025 16:09 View session

Copilot AI and others added 2 commits December 9, 2025 16:14

Recompile workflows after merging main branch

70622a7

Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>

Copilot finished work on behalf of pelikhan December 9, 2025 17:53

pelikhan marked this pull request as ready for review December 9, 2025 18:02

pelikhan reviewed Dec 9, 2025

View reviewed changes

Copilot started work on behalf of pelikhan December 9, 2025 18:04 View session

pelikhan added the smoke label Dec 9, 2025

github-actions Bot added the smoke-claude label Dec 9, 2025

Add changeset for actions build tooling [skip-ci]

f6d4875

github-actions Bot added the smoke-copilot label Dec 9, 2025

Copilot finished work on behalf of pelikhan December 9, 2025 18:12

Copilot AI requested a review from pelikhan December 9, 2025 18:12

Copilot started work on behalf of pelikhan December 9, 2025 18:39 View session

Add actions directory structure and Go-based build tooling for custom…

ef8596d

… GitHub Actions Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>

Copilot finished work on behalf of pelikhan December 9, 2025 18:50

pelikhan merged commit 9fa09ab into main Dec 9, 2025
4 checks passed

pelikhan deleted the copilot/create-actions-directory-structure branch December 9, 2025 18:51

Copilot AI mentioned this pull request Dec 29, 2025

Remove obsolete action references and clean up actions build system #8055

Merged

Conversation

Copilot AI commented Dec 9, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Plan: Create Actions Directory Structure and Build Tooling

Understanding

Checklist

Summary

Key Features

Build System Architecture

CI Integration

Documentation

Next Steps (Future Work)

Context

Tasks

Files to Create/Modify

Acceptance Criteria

Comments on the Issue (you are @copilot in this section)

Changeset

Uh oh!

pelikhan commented Dec 9, 2025

Uh oh!

Copilot AI commented Dec 9, 2025

Uh oh!

pelikhan commented Dec 9, 2025

Uh oh!

Copilot AI commented Dec 9, 2025

Uh oh!

pelikhan commented Dec 9, 2025

Uh oh!

Copilot AI commented Dec 9, 2025

Uh oh!

pelikhan commented Dec 9, 2025

Uh oh!

Copilot AI commented Dec 9, 2025

Uh oh!

Copilot AI commented Dec 9, 2025

Uh oh!

pelikhan Dec 9, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Dec 9, 2025

Choose a reason for hiding this comment

Uh oh!

pelikhan Dec 9, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Dec 9, 2025

Choose a reason for hiding this comment

Uh oh!

github-actions Bot commented Dec 9, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions Bot commented Dec 9, 2025

Uh oh!

github-actions Bot commented Dec 9, 2025

Uh oh!

github-actions Bot commented Dec 9, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions Bot commented Dec 9, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions Bot commented Dec 9, 2025 • edited by agentic-workflows-dev Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions Bot commented Dec 9, 2025

Smoke Test Results

Uh oh!

github-actions Bot commented Dec 9, 2025

Uh oh!

github-actions Bot commented Dec 9, 2025

Smoke Test Results

Uh oh!

pelikhan commented Dec 9, 2025

Uh oh!

Copilot AI commented Dec 9, 2025

Uh oh!

Uh oh!

Reviewers

Assignees

Copilot AI commented Dec 9, 2025 •

edited

Loading

github-actions Bot commented Dec 9, 2025 •

edited

Loading

github-actions Bot commented Dec 9, 2025 •

edited

Loading

github-actions Bot commented Dec 9, 2025 •

edited

Loading

github-actions Bot commented Dec 9, 2025 •

edited by agentic-workflows-dev Bot

Loading