What types of GitHub errors does this skill handle?

It handles token expiration (401), permission errors (403), rate limits (429), network failures, and validation errors (422) within your automation scripts.

Does this skill help with GitHub App permission issues?

Yes, it classifies 403 errors to help identify specifically when an app is missing necessary repository permissions or installation scopes.

How does this skill manage API rate limiting?

It follows a four-step strategy: Detect the 429 code, classify it as a retryable error, apply exponential backoff, and escalate if the limit persists.

Can I use this for non-GitHub workflows?

While optimized for GitHub App tokens and Actions, the patterns of retry logic and status code classification are applicable to most REST API integrations.

GitHub Action Error Handling

Name: GitHub Action Error Handling
Author: adaptive-enforcement-lab

byadaptive-enforcement-lab

Deployment & DevOps

Manages GitHub App tokens and API failures in workflows using robust retry logic and actionable error reporting.

About

This skill optimizes GitHub Actions workflows by implementing sophisticated error handling strategies for GitHub App tokens and API interactions. It provides a structured framework to detect, classify, and resolve common automation hurdles such as token expiration, permission mismatches, and rate limiting. By incorporating exponential backoff for transient errors and providing clear escalation paths for permanent failures, it ensures more resilient CI/CD pipelines and reduces manual debugging time for DevOps teams.

Key Features

Validation check (422) handling for invalid request payloads
Automated token expiration (401) detection and resolution logic
0 GitHub stars
Actionable error messaging for rapid escalation of permanent failures
Permission error (403) classification for scope troubleshooting
Exponential backoff retry strategy for API rate limits (429)

Use Cases

Hardening CI/CD pipelines against transient network issues and platform instability
Debugging complex permission scopes for automated GitHub App integrations
Scaling GitHub Actions that interact heavily with the GitHub REST or GraphQL APIs

About

Key Features

Validation check (422) handling for invalid request payloads
Automated token expiration (401) detection and resolution logic
0 GitHub stars
Actionable error messaging for rapid escalation of permanent failures
Permission error (403) classification for scope troubleshooting
Exponential backoff retry strategy for API rate limits (429)

Use Cases

Hardening CI/CD pipelines against transient network issues and platform instability
Debugging complex permission scopes for automated GitHub App integrations
Scaling GitHub Actions that interact heavily with the GitHub REST or GraphQL APIs