Hoverkraft GitHub Actions and Reusable Workflows

website·Indexed 30 days ago

https://docs.hoverkraft.cloud

Documentation for a collection of GitHub Actions and reusable workflows, including ci-github-publish for release management and ArgoCD deployments, ci-github-container for Docker image builds, and ci-github-nodejs for linting and testing. Features specialized actions for release planning, changelog summarization, Lighthouse URL checks, and OVH MKS scaling.

Tokens
111.5K
Snippets
477
Records
753
Agent score
50%

What's inside Hoverkraft

  1. Overview of the Hoverkraft Methodology

    The Hoverkraft methodology is a framework of practices, tools, and workflows designed for efficient, high-quality software development. It is built on six core pillars: Modularity (reusable components), Consistency (standardized approaches), Automation (CI/CD), Quality (built-in checks), Security (security-first approach), and Community (open-source collaboration).
  2. Overview of Clean Deploy - ArgoCD App Of Apps workflow

    The clean-deploy-argocd-app-of-apps reusable workflow is used to clean a deployment in an ArgoCD App Of Apps Pattern context. It is typically triggered by a repository_dispatch event with the event type clean-deploy. The expected payload for the dispatch event includes the repository name and the environment name.
    {
      "event_type": "clean-deploy",
      "client_payload": {
        "repository": "repository name (e.g. my-repository)",
        "environment": "environment name (e.g. production, review-apps:pr-1234)"
      }
    }
  3. Overview of the Hoverkraft open-source ecosystem

    Hoverkraft (also known as openkraft) is a collection of open-source projects dedicated to building developer-friendly tools and technologies. The ecosystem provides high-quality, well-documented software aimed at empowering developers.
  4. Overview of Hoverkraft Golden Paths

    Hoverkraft Golden Paths are opinionated sequences for setting up new repositories with a standardized structure, workflows, and configurations. They leverage reusable components to automate CI/CD, releases, and maintenance, ensuring consistency across projects and reducing the infrastructure burden on developers. Key benefits include built-in semantic PR validation, automated testing, security scanning, and Dependabot integration for keeping workflows and dependencies current.
  5. Overview of the release-actions reusable workflow

    The release-actions reusable workflow automatically detects changes in GitHub Actions and workflow files, generates or updates their corresponding README documentation (including version updates), and publishes these changes back to the repository via a pull request. When pushed to the default branch, it publishes the documentation to GitHub Pages.
  6. Overview of the testcontainers-node test runner

    The testcontainers-node image provides a consistent environment for running integration tests against other Docker images. It is based on Node.js 25 Alpine and includes the testcontainers library and its dependencies. Tests are executed via Docker, and test files are mounted at runtime from the specific image directories rather than being baked into the image.
  7. Overview of the clean-deploy reusable workflow

    The clean-deploy reusable workflow is designed to remove one or more deployments and execute a follow-up cleanup action (e.g., a repository-dispatch event) to handle repository-specific cleanup. It can be triggered on-demand via a specific comment trigger (defaulting to /undeploy).

    Key behaviors include:

    • Deleting matching deployments using a local action.
    • Exposing deleted environments in the environments step output.
    • Optionally triggering a configured clean action and posting a summary comment if environments were deleted.