ci: pass repo owners to run-tests.yml for fork-account matching

[jnasbyupgrade]

Pairs with pgxntool-test PR: Postgres-Extensions/pgxntool-test#25

Problem

CI resolved the paired sibling branch using github.repository_owner
(Postgres-Extensions), so a fork PR never found its paired branch (which
lives on the fork) and tested against the wrong, unpaired code. This is what
made the fix-38 PRs' CI fail: pgxntool-test's resolve looked for the pgxntool
branch on Postgres-Extensions, didn't find it (it was on the fork), fell back to
pgxntool=master, and master lacked the paired change.

This PR (pgxntool side)

When pgxntool runs its own tests (commit-with-no-tests or master-to-master),
pass explicit owners to run-tests.yml:

• pgxntool-owner = this PR's head account (the fork for fork PRs)
• pgxntool-test-owner = Postgres-Extensions (canonical master only — never a fork's master)

The matching resolve/owner logic and the pgxntool-owner/pgxntool-test-owner
inputs on run-tests.yml are in the paired pgxntool-test PR.

Merge order: pgxntool-test first (so run-tests.yml@master gains the owner
inputs), then this PR.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@jnasbyupgrade, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 19 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 07e23b23-9fa3-4105-8aed-acd435649a65

📥 Commits

Reviewing files that changed from the base of the PR and between b062fca and e594f85.

📒 Files selected for processing (3)

• .github/workflows/ci.yml
• README.asc
• README.html

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[Copilot]

Pull request overview

Updates this repo’s CI reusable-workflow invocation so fork PRs can pass the correct repository owners into pgxntool-test’s run-tests.yml, enabling correct paired-branch resolution across fork accounts.

Changes:

• Pass pgxntool-owner as the PR head repo owner (github.event.pull_request.head.repo.owner.login) to support fork PR pairing.
• Pass pgxntool-test-owner as the canonical Postgres-Extensions owner when falling back to pgxntool-test/master.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.