CI history

  • #10Dec 14, 2023Nazir Bilal Yavuz
  • #5Sep 25, 2023Nazir Bilal Yavuz
  • #1Sep 07, 2023Nazir Bilal Yavuz
  • #10Dec 14, 2023
    v3-0001-If-the-changes-are-only-in-the-README-files-skip-.patch
  • #5Sep 25, 2023
    v2-0002-Skip-CI-if-changes-are-only-in-docs-or-in-the-REA.patch
    v2-0001-Only-built-the-docs-if-there-are-changes-are-in-t.patch
  • #1Sep 07, 2023
    v1-0001-Only-built-the-docs-if-there-are-changes-are-in-t.patch
    v1-0002-Just-run-the-Build-the-Docs-task-if-the-changes-a.patch

Beta feature Hackorum builds and tests every patch posted to the lists, not only commitfest submissions. This is Hackorum's own CI rather than the PostgreSQL project's, and it is still under testing - please report anything that looks wrong.

won't retrysuccessCI history

You can run a PostgreSQL built from this patch straight from Docker, with no checkout and no build:

docker run --rm -p 5432:5432 ghcr.io/hackorum-dev/postgres-patch:t48424
psql -h localhost -U postgres

Built from patchset v10 (message #10), July 27, 2026 at 11:39 PM.

Every patchset is also pushed to a branch of our PostgreSQL fork, so you can check out the same tree CI built. Without a PostgreSQL checkout:

git clone --branch t48424_10 https://github.com/hackorum-dev/postgres.git

In a checkout you already have, add the fork once:

git remote add hackorum https://github.com/hackorum-dev/postgres.git

then, for this patchset and every later one:

git fetch hackorum t48424_10 && git checkout t48424_10

Patchset v10 (message #10) is on t48424_10