Important
This repository is no longer the source of the Commit Check website.
The documentation, the landing page and the blog now live at commit-check.com, built from commit-check/commit-check.com.
Open issues and pull requests about the website there, not here.
It is kept as the historical source of the old site. The docs/ directory is
still here and still readable, but it is no longer published.
What commit-check.github.io serves is a set of redirect stubs — one for every
URL the old site had — pointing at the page that replaced it. The pages, the
blog and its archive, author and category indexes all kept their paths, so the
redirects are one-to-one; /projects/ is the exception, having been folded into
the Ecosystem section of the new landing page.
| Old URL | Now |
|---|---|
commit-check.github.io/ |
commit-check.com/ |
commit-check.github.io/getting-started/ |
commit-check.com/getting-started/ |
commit-check.github.io/blog/… |
commit-check.com/blog/… — same paths |
commit-check.github.io/projects/ |
commit-check.com/ |
The redirects are generated by scripts/build_redirects.py, and tests/
verifies the map still covers every URL the old site served. GitHub Pages has
no server-side redirect table, so each stub is a rel=canonical plus a
<meta refresh> — the canonical is what moves search ranking to the new URL.
Two hosts serve this repository, so both are covered: GitHub Pages gets the
stubs, and netlify.toml gives the Netlify project real 301s and stops it
building the old site from a command configured in its web UI.
Archiving a repository makes it read-only and stops its Actions from running, but it does not unpublish its GitHub Pages site: whatever was deployed last keeps being served. So the redirects have to be deployed before the archive switch is flipped. Afterwards there is no way to change what this domain serves without unarchiving first.