Removing Scheme from Workflow

[leogdion]

No description provided.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 5593c2dc-a9b3-4070-bfe4-043a24b610b2

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch 403-remove-scheme-from-workflows

---

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 and usage tips.}

[claude]

Code Review

Overview

This PR removes explicit scheme parameters from five brightdigit/swift-build@v1 action invocations across two workflow files, addressing issue #403. The intent is to let the action use its own default scheme detection rather than an explicitly specified scheme.

---

What's Good

• Correct direction for consistency: Before this PR, several swift-build invocations (WASI, Windows, Android in MistKit.yml) already omitted scheme. After this PR, all invocations are uniform — no scheme passed anywhere.
• Minimal, surgical diff: 5 line deletions, no additions — low risk of unintended side-effects.

---

Issues / Suggestions

1. Missing PR description
The PR body is empty. Even a one-liner like "The brightdigit/swift-build@v1 action now auto-detects the scheme; passing it explicitly causes X" would make the intent clear to reviewers and future git blame readers. Consider filling in the body.

2. Inconsistency being silently fixed
Before this PR, MistDemo.yml passes two different scheme values:

• Android step: scheme: ${{ env.PACKAGE_NAME }} → MistDemo
• macOS steps: scheme: ${{ env.PACKAGE_NAME }}-Package → MistDemo-Package

That's an existing bug being cleaned up here, but it isn't called out. It would be worth noting in the PR description that the Android build was using a potentially wrong scheme name.

3. No test/validation evidence
Since this changes CI configuration, it would be reassuring to see a note (or link to a successful run) confirming the workflows still pass without the scheme input. If the action silently ignores unknown or missing inputs, a green run after this change is the only proof the removal is safe.

4. Branch target
This is targeting v1.0.0-beta.3 rather than main. If the same scheme parameters exist on main, a follow-up PR will be needed there — worth tracking.

---

Summary

The change itself is correct and low-risk. Main asks before merging:

1. Add a brief PR description explaining why scheme is being removed (action change? was it causing failures?).
2. Link or paste a successful CI run demonstrating the workflows pass without scheme.
3. Confirm whether a matching change to main is needed.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (v1.0.0-beta.3@6d23e40). Learn more about missing BASE report.

Additional details and impacted files

@@               Coverage Diff                @@
##             v1.0.0-beta.3     #404   +/-   ##
================================================
  Coverage                 ?   71.69%           
================================================
  Files                    ?      168           
  Lines                    ?     3844           
  Branches                 ?        0           
================================================
  Hits                     ?     2756           
  Misses                   ?     1088           
  Partials                 ?        0           

Flag	Coverage Δ
mistdemo-spm-macos	11.42% <ø> (?)
mistdemo-swift-6.2-jammy	11.42% <ø> (?)
mistdemo-swift-6.2-noble	11.55% <ø> (?)
mistdemo-swift-6.3-jammy	11.42% <ø> (?)
mistdemo-swift-6.3-noble	11.42% <ø> (?)
spm	71.55% <ø> (?)
swift-6.1-jammy	71.67% <ø> (?)
swift-6.1-noble	71.57% <ø> (?)
swift-6.2-jammy	71.59% <ø> (?)
swift-6.2-noble	71.57% <ø> (?)
swift-6.3-jammy	71.73% <ø> (?)
swift-6.3-noble	71.65% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.