Give each platform its own CI workflow and badge - #53
Merged
Conversation
🦋 Changeset detectedLatest commit: 093dfc7 The changes in this PR will be included in the next version bump. This PR includes changesets to release 0 packagesWhen changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
germ-mark
force-pushed
the
ci/platform-badges
branch
from
August 17, 2026 23:30
4c91be8 to
4521629
Compare
germ-mark
changed the title
GitHub's workflow badges are workflow-scoped, so a badge can only be as specific as the workflow it points at. Naming this one Apple lets the README state which platform is actually covered, and leaves room for ci-linux.yml / ci-android.yml to land beside it.
An Apple-only badge says nothing about the platforms the package is being ported to. Matches GermConvenience, whose three legs are green on main. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
germ-mark
force-pushed
the
ci/platform-badges
branch
from
August 18, 2026 00:06
4521629 to
c09dddc
Compare
Push and pull_request events land in different concurrency groups, so an open PR ran every leg twice per commit. Filtering push to main leaves one run per PR commit plus the badge run on merge. Linux pins swift:6.2 — the package's declared toolchain floor — instead of floating on latest. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
germ-mark
force-pushed
the
ci/platform-badges
branch
from
August 18, 2026 01:48
c09dddc to
093dfc7
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Splits
ci.ymlintoci-apple.yml/ci-linux.yml/ci-android.yml, eachname:d for its platform, and puts all three badges in the README. No sourcechange, no release.
Stacked on #55 — the Linux and Android legs cannot pass without it, since
ServiceEndpoint.swiftimportsNetwork. Rebase ontomainonce that merges.Why
GitHub's Actions status badges are workflow-scoped — there is no per-job
filter, so a badge can only ever be as specific as the workflow it points at. A
workflow called
CIproduces a badge that says "CI", which tells a readernothing about which platforms are covered. Worse, an Apple-only badge on a
package being ported to Android reads as a portability claim it isn't making:
this repo has been failing to compile for Linux and Android since the PDS
hardening in #51, and nothing in CI said so.
The Apple job matrix and steps are unchanged. The Linux and Android legs are
copied from GermConvenience, with two deliberate divergences:
main. Push and pull_request events land indifferent concurrency groups, so an open PR ran every leg twice per commit.
PRs get one run per commit;
maingets the badge run on merge.swift:6.2— the package's declared tools-version floor —instead of floating on
swift:latest, so the badge proves the minimumtoolchain the package claims and can't flip red without a commit landing.
Notes
mainhas no branch protection, so no required status check is named after theold workflow and nothing breaks by renaming it.
mainuntil this merges, so the badges read"no status" until then. Self-healing on the first push after merge.
Part of GER-2175.
🤖 Generated with Claude Code