Add repository field to upload-assets configuration for cross-repository publishing - #945

Updating upload-asset to support custom GitHub repository and token

Problem Analysis ✅

The current upload-asset functionality only supports publishing to the same GitHub repository where the workflow is running. The requirement is to add support for specifying a different GitHub repository and GitHub token.

Implementation Complete ✅

Core Changes Implemented:

1. Added Repository field to UploadAssetsConfig struct in publish_assets.go
2. Updated parsing logic to handle the new repository field from YAML configuration
3. Modified URL generation in safe_outputs_mcp_server.cjs to use custom repository when specified
4. Enhanced upload script in upload_assets.cjs to handle cross-repository git operations with proper authentication
5. Updated all engines (Claude, Codex, Custom) to pass GITHUB_AW_ASSETS_REPOSITORY environment variable
6. Updated JSON schema to validate repository field with proper pattern matching (owner/repo format)

Recent Updates:

• ✅ Merged main branch to incorporate latest bug fixes and test improvements
• ✅ All tests now passing - resolved conflicts and test failures
• ✅ Code formatted and built successfully

Key Features:

• ✅ Repository field accepts format: owner/repo (validated by regex pattern)
• ✅ Automatically uses current repository if no custom repository specified
• ✅ Supports custom GitHub token for cross-repository access
• ✅ Handles git remotes and authentication for pushing to different repositories
• ✅ URL generation correctly points to the target repository for asset access
• ✅ Backward compatible - existing workflows continue to work unchanged

Testing & Validation:

• ✅ Added comprehensive test cases for parsing repository configuration
• ✅ Validated schema compilation with custom repository specifications
• ✅ Confirmed generated workflows include all necessary environment variables
• ✅ Tested both custom repository and default repository scenarios
• ✅ All unit tests passing after main branch merge
• ✅ Full integration testing with complete configuration options

Usage Example

---
on: workflow_dispatch
permissions:
  contents: read
engine: claude
safe-outputs:
  upload-assets:
    repository: "myorg/assets-repo"
    github-token: "${{ secrets.ASSETS_REPO_TOKEN }}"
    branch: "main"
    max-size: 5120
    allowed-exts: [".jpg", ".png", ".pdf"]
---

# Upload Assets to Custom Repository
Generate and upload assets to a separate repository.

Technical Implementation Details

• Environment Variable: GITHUB_AW_ASSETS_REPOSITORY passed to all engine configurations
• Git Operations: Custom remote setup for cross-repository pushing with token authentication
• URL Generation: Uses custom repository in raw.githubusercontent.com URLs
• Schema Validation: Regex pattern ensures proper owner/repo format
• Fallback Behavior: Gracefully defaults to current repository when not specified

Status: ✅ COMPLETE, TESTED, AND READY FOR MERGE

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.