What do you hate the most about GitHub Actions?

The most frustrating aspect of GitHub Actions is undoubtedly the debugging experience, which is notoriously opaque and time-consuming. Here’s why it’s universally hated:

1. ·Logs are truncated or fragmented: Errors often appear without meaningful context, forcing developers to rely on trial-and-error commits. Long logs are folded in the UI, requiring repetitive clicks to uncover the full output.
2. ·No live debugging: Without SSH access to runners, you can’t inspect the environment mid-failure unless you resort to self-hosted runners or custom workarounds.
3. ·Vague error messages: Common errors like 'Process completed with exit code 1' provide no actionable insight, leaving you to add ad-hoc echo statements or upload artifacts to piece together what went wrong.

Beyond debugging, GitHub Actions has several other pain points that compound frustration:

YAML Configuration Complexity

• ·The YAML syntax is verbose and brittle. Minor indentation errors or stray characters can silently break workflows.
• ·Reusing logic across workflows is cumbersome, requiring reusable workflows or composite actions, which add layers of indirection.
• ·Large YAML files become unmaintainable, making onboarding and troubleshooting painful.

Slow Startup Times and Resource Limits

• ·Runners can take minutes to provision, especially for macOS or Windows. Queue delays are unpredictable, stalling development workflows.
• ·Free-tier users face strict concurrency limits (20 jobs per repo) and minute quotas (2,000/month for public repos, 500 for private repos), which can halt pipelines during peak periods.

Cost Ambiguity

• ·Windows runners cost 2x and macOS runners 10x the standard rate, leading to unexpected bills.
• ·Artifact storage costs can balloon silently, especially for large logs or build outputs.

Runner Environment Inconsistency

• ·Hosted runners are refreshed daily, requiring reinstallation of custom tools each run.
• ·Differences between runner images (Ubuntu, Windows, macOS) can cause 'works on my machine' bugs.

Mitigation Strategies

To alleviate these issues, consider:

• ·Using actions/upload-artifact to persist intermediate files for debugging.
• ·Splitting large workflows into smaller, reusable files (.github/workflows/build.yml, test.yml).
• ·Aggressively caching dependencies with actions/cache to reduce runner provisioning time.
• ·Pinning runner image versions (ubuntu-22.04) and using container: for reproducible environments.

In summary, while GitHub Actions is a powerful automation tool, its debugging challenges and YAML complexity often turn CI/CD into a time sink rather than a productivity booster. Addressing these pain points can make it a more effective platform for teams.