ci: run iOS SDK CI on pull requests to any base branch

[ajaysubra]

Description

The iOS SDK CI workflow (swift.yml) only ran its build + test jobs for PRs whose base branch matched the glob branches: ['*']. In GitHub Actions branch filters, * matches master but does not match any branch containing / (** is required for that). So every PR stacked onto a feature or personal base — feat/*, {initials}/* — silently skipped the entire build/test matrix:

• library-macos-14 (Xcode 15.2, 15.4)
• library-macos-15 (Xcode 16.4)

Those stacked PRs only ran pre-commit and the bot scanners, giving an all-green status with no compile or test coverage.

How this surfaced

Reviewing #587 (base feat/auto-push-tracking), the test target would fail to compile on Xcode 15.x, yet PR checks were green — because swift.yml never ran. gh run list --workflow swift.yml for that branch returns zero runs, and the status rollup contains only pre-commit + scanners.

Change

Drop the branches filter under pull_request: so the workflow runs on every PR regardless of base branch — mirroring pre-commit.yml, which already does this and consequently runs everywhere. push remains scoped to master. Removing the glob also eliminates the *-vs-** foot-gun entirely.

   pull_request:
-    branches:
-      - '*'
   workflow_dispatch:

Test Plan

• On this PR (base master), confirm library-macos-14 / library-macos-15 run as before — no regression on master-targeting PRs.
• Open or re-run a PR with a slashed base (e.g. a feat/* base) and confirm the build/test jobs now trigger.

Notes

• codeql.yml has a related but intentional scoping (branches: ['master', 'rel/*']) and is left unchanged — expanding a heavy security scan to all PRs is a separate, cost-conscious decision.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Updated CI/CD workflow configuration to run on a specific branch.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Enterprise

Run ID: 391b2758-3282-452d-90ac-941d685926d6

📥 Commits

Reviewing files that changed from the base of the PR and between 0b24232 and 9ab5e7c.

📒 Files selected for processing (1)

• .github/workflows/swift.yml

💤 Files with no reviewable changes (1)

• .github/workflows/swift.yml

---

📝 Walkthrough

Walkthrough

The GitHub Actions Swift workflow push trigger is narrowed to run only on the master branch instead of all branches. The change replaces the wildcard branch pattern with an explicit master-branch-only filter, leaving all workflow jobs and steps unchanged.

Changes

CI Workflow Trigger Narrowing

Layer / File(s)	Summary
Push trigger branch filter .github/workflows/swift.yml	The on.push.branches configuration is updated from wildcard matching to explicit master branch targeting.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A rabbit hops through CI flows,
Master branch is where the action goes!
No more wildcards in the night,
Just clean, focused builds done right. 🐰✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: enabling iOS SDK CI to run on pull requests targeting any base branch, not just master.
Description check	✅ Passed	The description is well-structured and covers most required sections with substantial detail about the problem, solution, and testing approach.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch ci/run-swift-ci-on-all-prs

---

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