This repository has no CODEOWNERS file, so GitHub never auto-requests a reviewer on any pull request here.
Probe — the endpoint distinguishes the three states, and this repo is in the third:
gh api repos/spiceai/cookbook/codeowners/errors
# HTTP 404 — no CODEOWNERS file exists (as opposed to {"errors":[]} = working, or a populated
# errors array = the file exists but a rule names something unresolvable)
gh api repos/spiceai/cookbook/contents/CODEOWNERS # 404
gh api repos/spiceai/cookbook/contents/.github/CODEOWNERS # 404Effect, measured 2026-08-14T14:1xZ: all 4 open non-draft PRs have reviewRequests: []. They are not failing anything — they are mergeable with green checks and simply have nobody asked to look at them, so they age until someone happens to browse the list.
This is the same symptom as spiceai/docs#2097 and spiceai/spicepy#186, but not the same cause: those repos have a CODEOWNERS file naming a team GitHub cannot resolve, which is a one-line correction. Here the file is absent, so the fix is a decision about who owns review for this repo rather than a typo — which is why this is an issue rather than a PR.
Suggested fix, matching what already resolves elsewhere in the org (spiceai/spiceai uses this team and its codeowners/errors returns 0):
# Repo maintainers
* @spiceai/spice-core-maintainers
Worth confirming that team is the intended owner for cookbook recipes specifically before it lands — if recipe review should sit with a different group, that group's team slug goes here instead.
Related: spiceai/docs#2097, spiceai/spicepy#186, spicehq/website#306.
This repository has no
CODEOWNERSfile, so GitHub never auto-requests a reviewer on any pull request here.Probe — the endpoint distinguishes the three states, and this repo is in the third:
Effect, measured 2026-08-14T14:1xZ: all 4 open non-draft PRs have
reviewRequests: []. They are not failing anything — they are mergeable with green checks and simply have nobody asked to look at them, so they age until someone happens to browse the list.This is the same symptom as spiceai/docs#2097 and spiceai/spicepy#186, but not the same cause: those repos have a
CODEOWNERSfile naming a team GitHub cannot resolve, which is a one-line correction. Here the file is absent, so the fix is a decision about who owns review for this repo rather than a typo — which is why this is an issue rather than a PR.Suggested fix, matching what already resolves elsewhere in the org (
spiceai/spiceaiuses this team and itscodeowners/errorsreturns0):Worth confirming that team is the intended owner for cookbook recipes specifically before it lands — if recipe review should sit with a different group, that group's team slug goes here instead.
Related: spiceai/docs#2097, spiceai/spicepy#186, spicehq/website#306.