lucky-deploy-recovery

Diagnose failed Lucky homelab deployments, clean git repositories, and rerun workflows.

17|8|Updated Apr 11, 2022

Search Tags:#git #deployment #troubleshooting #github actions #recovery #homelab

Ready to run

npx skills add https://github.com/LucasSantana-Dev/Lucky --skill lucky-deploy-recovery

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: lucky-deploy-recovery
Source: https://github.com/LucasSantana-Dev/Lucky/tree/main/.cursor/skills/lucky-deploy-recovery
Command: npx skills add https://github.com/LucasSantana-Dev/Lucky --skill lucky-deploy-recovery

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps to unblock and recover failed deployments of the Lucky application to a homelab environment, specifically addressing issues like webhook lock contention, dirty code checkouts, or pre-runtime check failures.

Core Features & Use Cases

Diagnose Deployment Failures: Identifies the root cause of 'Deploy to Homelab' failures.
Automate Recovery Steps: Executes commands to resolve common issues like git conflicts and concurrent deploy locks.
Rerun and Verify: Facilitates rerunning the deployment workflow and performing post-deploy health checks.
Use Case: When the 'Deploy to Homelab' GitHub Actions workflow fails due to a LOCK_CONTENTION error, this skill can be used to safely clear the lock and re-trigger the deployment.

Quick Start

Use the lucky-deploy-recovery skill to unblock a failed Lucky deployment.

Frequently Asked Questions about lucky-deploy-recovery

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I fix a failed GitHub Actions deployment caused by webhook lock contention?▼

To fix a failed GitHub Actions deployment caused by webhook lock contention, you need to diagnose the failure, clear the concurrent deploy lock on the target host, and rerun the deployment workflow.

Why does my git deployment to a homelab fail with a dirty checkout drift error?▼

Your git deployment to a homelab fails with a dirty checkout drift error due to uncommitted changes or conflicts in the target server's repository. Resolving it requires cleaning up the dirty checkout before rerunning the workflow.

What is the best way to automate recovery for a failed homelab application deployment?▼

Automating recovery for a failed homelab application deployment involves diagnosing precheck failures, cleaning the target host's git repository, and re-triggering the deployment workflow automatically.

Do I need SSH access to rerun a failed GitHub Actions deployment workflow to my homelab?▼

Yes, you need SSH access to the target server to manage the host's git repository directly. You also need the GitHub CLI installed to manage and rerun the deployment workflow effectively.

Can I clear a deployment lock on my homelab server without manual SSH cleanup?▼

Clearing a deployment lock on a homelab server safely without manual SSH cleanup requires an automated recovery process that connects via SSH to resolve the contention and re-trigger the workflow.

What should I do when my homelab deployment precheck fails before runtime?▼

When your homelab deployment precheck fails before runtime, you should diagnose the specific precheck failure, clean up the target host environment, and rerun the GitHub Actions deployment workflow.