From a8cb5a4c7176888b7b3f2a1ea282ce792b16d1de Mon Sep 17 00:00:00 2001 From: jnasbyupgrade Date: Mon, 13 Jul 2026 14:21:55 -0500 Subject: [PATCH 1/4] ci: pass repo owners to run-tests.yml (fork-account matching) Pairs with the pgxntool-test change. When pgxntool runs its own tests (commit-with-no-tests or master-to-master), pass pgxntool-owner = this PR's head account (a fork for fork PRs) and pgxntool-test-owner = Postgres-Extensions, so fork PRs check out their own pgxntool branch and always take pgxntool-test from canonical master rather than a fork's master. Co-Authored-By: Claude Opus 4.8 (1M context) --- .github/workflows/ci.yml | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index ac30308..9e3ce90 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -285,5 +285,10 @@ jobs: # ----------------------------------------------------------------------- uses: Postgres-Extensions/pgxntool-test/.github/workflows/run-tests.yml@master with: + # pgxntool: this PR's own branch, on its own account (a fork for fork PRs). + pgxntool-owner: ${{ github.event.pull_request.head.repo.owner.login }} pgxntool-branch: ${{ github.event.pull_request.head.ref }} + # pgxntool-test: no paired test PR in this path, so use canonical master + # from Postgres-Extensions only (never a fork's master). + pgxntool-test-owner: Postgres-Extensions pgxntool-test-ref: master From 63522e51b6dfbf25f75327eee1e27616f4cafda6 Mon Sep 17 00:00:00 2001 From: jnasbyupgrade Date: Mon, 13 Jul 2026 15:46:46 -0500 Subject: [PATCH 2/4] ci: no-op commit to trigger extra tests (reverted next) --- .ci-trigger | 1 + 1 file changed, 1 insertion(+) create mode 100644 .ci-trigger diff --git a/.ci-trigger b/.ci-trigger new file mode 100644 index 0000000..5c33b15 --- /dev/null +++ b/.ci-trigger @@ -0,0 +1 @@ +trigger From f5dd18a271964a3abc40afd037e82123a1cd633a Mon Sep 17 00:00:00 2001 From: jnasbyupgrade Date: Mon, 13 Jul 2026 15:46:46 -0500 Subject: [PATCH 3/4] Revert "ci: no-op commit to trigger extra tests (reverted next)" This reverts commit 63522e51b6dfbf25f75327eee1e27616f4cafda6. --- .ci-trigger | 1 - 1 file changed, 1 deletion(-) delete mode 100644 .ci-trigger diff --git a/.ci-trigger b/.ci-trigger deleted file mode 100644 index 5c33b15..0000000 --- a/.ci-trigger +++ /dev/null @@ -1 +0,0 @@ -trigger From e594f85194d216d27b630578ed79e969649e34e0 Mon Sep 17 00:00:00 2001 From: jnasbyupgrade Date: Mon, 13 Jul 2026 16:27:56 -0500 Subject: [PATCH 4/4] docs: update Development section for paired-branch workflow The README's Development section pointed at the old decibel/pgxntool-test URL and didn't mention how contributions are coordinated. Point at Postgres-Extensions/pgxntool-test and note that changes are normally paired across both repos (matching branch + account), linking to pgxntool-test's "CI and Contributing" section. Regenerated the matching README.html paragraph. Co-Authored-By: Claude Opus 4.8 (1M context) --- README.asc | 4 +++- README.html | 5 ++++- 2 files changed, 7 insertions(+), 2 deletions(-) diff --git a/README.asc b/README.asc index 03b9acc..db6162f 100644 --- a/README.asc +++ b/README.asc @@ -25,7 +25,9 @@ TODO: Create a nice script that will init a new project for you. == Development -If you want to contribute to pgxntool development, work from the https://github.com/decibel/pgxntool-test[pgxntool-test] repository, not from this repository. That repository contains the test infrastructure and development tools needed to validate changes to pgxntool. This repository contains only the framework files that get embedded into extension projects via `git subtree`. +If you want to contribute to pgxntool development, work from the https://github.com/Postgres-Extensions/pgxntool-test[pgxntool-test] repository, not from this repository. That repository contains the test infrastructure and development tools needed to validate changes to pgxntool. This repository contains only the framework files that get embedded into extension projects via `git subtree`. + +Changes are normally paired across both repos: a `pgxntool` change should come with a matching branch (same name, on the same account) and PR in `pgxntool-test`, and CI enforces this pairing. See the https://github.com/Postgres-Extensions/pgxntool-test#ci-and-contributing[CI and Contributing] section in pgxntool-test for the full workflow. == Usage Typically, you can just create a simple Makefile that does nothing but include base.mk: diff --git a/README.html b/README.html index a46c633..431358f 100644 --- a/README.html +++ b/README.html @@ -542,7 +542,10 @@

2. Development

-

If you want to contribute to pgxntool development, work from the pgxntool-test repository, not from this repository. That repository contains the test infrastructure and development tools needed to validate changes to pgxntool. This repository contains only the framework files that get embedded into extension projects via git subtree.

+

If you want to contribute to pgxntool development, work from the pgxntool-test repository, not from this repository. That repository contains the test infrastructure and development tools needed to validate changes to pgxntool. This repository contains only the framework files that get embedded into extension projects via git subtree.

+
+
+

Changes are normally paired across both repos: a pgxntool change should come with a matching branch (same name, on the same account) and PR in pgxntool-test, and CI enforces this pairing. See the CI and Contributing section in pgxntool-test for the full workflow.