test: run test_github_api_integration test only on Ubuntu to avoid rate limits

[anakin87]

Related Issues

Flaky test reported in #10341 (comment)

This test likely failed because another test workflow ran at the same time.

In fact, GitHub REST API rate limits for search operations (like the one used in the test) are quite low; they are lower than limits on core operations.

Proposed Changes:

• run the integration test only on Ubuntu to avoid hitting rate limits

How did you test it?

CI

Notes for the reviewer

After discussion with @julian-risch, we decided it's useful to have an integration test but we only run it on Ubuntu to avoid rate limits

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.

Project	Deployment	Review	Updated (UTC)
haystack-docs	Ready	Preview, Comment	Jan 26, 2026 2:40pm

[coveralls]

Pull Request Test Coverage Report for Build 21361613535

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 92.446%

---

Totals
Change from base Build 21353884971:	0.0%
Covered Lines:	14758
Relevant Lines:	15964

---

💛 - Coveralls