git404hub

what is health-check-action fr?

jamesmortensen/health-check-action — explained in plain English

Analysis updated 2026-07-18 · repo last pushed 2023-01-11

Audience · ops devopsComplexity · 1/5DormantSetup · easy

tl;dr

A GitHub Actions tool that pings your website to check it's online, failing the workflow if the site doesn't respond in time.

vibe map

mindmap
  root((repo))
    What it does
      Checks site is up
      Fails workflow on timeout
      Optional version check
    Tech stack
      GitHub Actions
      curl
      wget
    Use cases
      Uptime alerts
      Post deploy check
      Scheduled monitoring
    Audience
      Startups
      Site owners
      DevOps teams

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

what do people make with this?

VIBE 1

Alert your team automatically when your live website goes down.

VIBE 2

Run a health check every 15 minutes on your landing page.

VIBE 3

Verify a new version deployed successfully after a release.

VIBE 4

Add an uptime check step to an existing deployment workflow.

what's the stack?

GitHub Actionscurlwget

how it stacks up fr

jamesmortensen/health-check-action0verflowme/alarm-clock0verflowme/seclists
LanguageCSS
Last pushed2023-01-112022-10-032020-05-03
MaintenanceDormantDormantDormant
Setup difficultyeasyeasyeasy
Complexity1/52/51/5
Audienceops devopsvibe coderops devops

Figures from each repo's GitHub metadata at analysis time.

how do i run it?

Difficulty · easy time til it works · 5min

in plain english

This is a tool that automatically checks whether a website is up and running. You add it to your GitHub workflow (a series of automated tasks that run when you push code or on a schedule), point it at your website's URL, and it will test whether the site is reachable. If the site responds within the time limit, the check passes. If it doesn't respond, the workflow fails and you know there's a problem. The action works by sending a simple request to your website using either curl or wget, two common command-line tools for fetching web pages. By default, it waits up to 5 minutes (300 seconds) for the site to respond. You can change that timeout if you want it to fail faster or give the site more time. It can also optionally look for a specific version name in your website's HTML if you need to verify that a particular version is deployed. You'd use this if you're running a live website and want to get notified automatically when it goes down. For example, a startup might set this to run every 15 minutes on their main landing page, so their team gets alerted instantly if there's an outage. Or after deploying a new version, you could run this check as part of your deployment process to make sure the site actually came back up after the update. The README doesn't go into detail about how it integrates with broader monitoring or notification systems, so it appears to be a building block you'd combine with GitHub's existing alerting features rather than a complete uptime monitoring solution on its own.

prompts (copy fr)

prompt 1
Add jamesmortensen/health-check-action to my GitHub Actions workflow to check my website every 15 minutes.
prompt 2
Show me how to configure health-check-action to fail if my site doesn't respond within 60 seconds.
prompt 3
Set up health-check-action to run after my deploy job and verify a specific version string is on the page.
prompt 4
Help me combine health-check-action with GitHub Actions notifications so my team gets alerted on downtime.

Frequently asked questions

what is health-check-action fr?

A GitHub Actions tool that pings your website to check it's online, failing the workflow if the site doesn't respond in time.

Is health-check-action actively maintained?

Dormant — no commits in 2+ years (last push 2023-01-11).

How hard is health-check-action to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is health-check-action for?

Mainly ops devops.

peek the repo → explain another one

This repo across BitVibe Labs

double-check against the repo, no cap.