gh add: better tracking of added/modified files

[Copilot]

This PR implements comprehensive file tracking and explicit rollback functionality for the gh aw add --pr command, while enhancing user experience with consistent console formatting and simplifying the API.

Problem

The current add --pr command had several issues:

1. Only staged files from .github/workflows/ directory, missing other generated files
2. No automatic cleanup when git operations failed, leaving orphaned files
3. Inconsistent console output with plain text messages
4. Unnecessary backward compatibility layer cluttering the API

Solution

File Tracking & Explicit Rollback

• Tracks all file operations during workflow addition (markdown files, lock files, .gitattributes, includes)
• Provides explicit rollback on git operation failures with original content restoration at each error point
• Ensures proper staging of all tracked files for complete commits
• Improved error handling by replacing defer-based rollback with explicit rollback calls for better control flow

Enhanced User Experience

• Consistent console formatting using the console package throughout the codebase
• Styled error messages with ✗ symbols going to stderr
• Informational messages with ℹ symbols for better visibility
• Success messages with ✓ symbols for positive feedback
• Warning messages with ⚠ symbols for non-critical issues

API Simplification

• Removed backward compatibility wrapper AddWorkflow function
• Streamlined API by having callers use AddWorkflowWithTracking directly
• Updated all tests to use the simplified API

Implementation

The solution uses a modular FileTracker architecture (in separate file pkg/cli/file_tracker.go) with explicit rollback pattern:

// Add workflow files using tracking logic
if err := AddWorkflowWithTracking(workflow, number, verbose, engineOverride, name, force, tracker); err != nil {
    if rollbackErr := tracker.RollbackAllFiles(verbose); rollbackErr != nil && verbose {
        fmt.Fprintln(os.Stderr, console.FormatWarningMessage(fmt.Sprintf("Failed to rollback files: %v", rollbackErr)))
    }
    return fmt.Errorf("failed to add workflow: %w", err)
}

This explicit approach provides better control over when rollback occurs and makes the error handling flow more transparent compared to defer-based cleanup.

Testing

All existing tests pass with the new implementation. The console formatting provides immediate visual feedback making it easier to identify issues during development and usage.

Fixes #33.

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.

[Copilot]

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

Warning

Firewall rules blocked me from connecting to one or more addresses

I tried to connect to the following addresses, but was blocked by firewall rules:

• api.contoso.com
  • Triggering command: /tmp/go-build3984810454/b256/cli.test -test.testlogfile=/tmp/go-build3984810454/b256/testlog.txt -test.paniconexit0 -test.timeout=10m0s -test.v=true (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[pelikhan]

@copilot apply console formatting helpers from the console package for error messages

[Copilot]

@copilot apply console formatting helpers from the console package for error messages

Applied console formatting helpers for error messages. Converted warning and error messages to use console.FormatWarningMessage(), console.FormatErrorMessage(), console.FormatSuccessMessage(), and console.FormatInfoMessage() throughout the codebase. Error messages now properly go to stderr with styled formatting. Commit c84acf2

Warning

Firewall rules blocked me from connecting to one or more addresses

I tried to connect to the following addresses, but was blocked by firewall rules:

• api.contoso.com
  • Triggering command: /tmp/go-build3945037323/b001/cli.test -test.testlogfile=/tmp/go-build3945037323/b001/testlog.txt -test.paniconexit0 -test.v=true -test.timeout=5m0s (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[Copilot]

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

Warning

Firewall rules blocked me from connecting to one or more addresses

I tried to connect to the following addresses, but was blocked by firewall rules:

• api.contoso.com
  • Triggering command: /tmp/go-build3426441333/b256/cli.test -test.testlogfile=/tmp/go-build3426441333/b256/testlog.txt -test.paniconexit0 -test.timeout=10m0s -test.v=true (dns block)
  • Triggering command: /tmp/go-build1111799091/b256/cli.test -test.testlogfile=/tmp/go-build1111799091/b256/testlog.txt -test.paniconexit0 -test.timeout=10m0s -test.v=true (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)