ci: stop asking reviews for API reference updates

[anakin87]

Related Issues

• related to https://github.com/deepset-ai/haystack-private/issues/217

Now that the API reference updates are automatically approved and merged by GitHub Bot (see #10853), we can reduce noise by stopping asking human reviewers.

Proposed Changes:

• remove the assigned reviewer from the API reference update workflow (we should also do this in core integrations and experimental)
• do not assign PRs touching API reference (which is totally automated) to human reviewers

How did you test it?

Hard to test it before merging, but it seems safe.

Checklist

• I have read the contributors guidelines and the code of conduct.
• I have updated the related issue with new insights and changes.
• I have added unit tests and updated the docstrings.
• I've used one of the conventional commit types for my PR title: fix:, feat:, build:, chore:, ci:, docs:, style:, refactor:, perf:, test: and added ! in case the PR includes breaking changes.
• I have documented my code.
• I have added a release note file, following the contributors guidelines.
• I have run pre-commit hooks and fixed any issue.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
haystack-docs	Ignored		Mar 18, 2026 2:24pm

[sjrl]

Looks good!