supabase / supabase-swift / 41106605598
96%

DEFAULT BRANCH: main
Ran
Jobs 1
Files 194
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 94.065% (+0.02%) from 94.045%
41106605598

push

github

web-flow 
chore: ignore root-level compiler intermediates (#1296)

A build once left 252 files in the repository root — `ASN1.o`, `ASN1.dia`,
`MuSig+Nonces.swiftdeps` and the like, 63 basenames times four extensions. The
63 match the shared sources of swift-secp256k1's `P256K` target one for one.
Nothing ignored them, so a `git add -A` committed them and the commit had to be
rewritten.

These belong in `.build/` or DerivedData, and both are configured correctly:
there is no `WorkspaceSettings.xcsettings` overriding the build location and
Xcode's build-location defaults are unset. The cause is upstream. `P256K` takes
its sources from a build-tool plugin's output directory, and SwiftPM bug #7930
then writes the per-file intermediates relative to the build process's working
directory. SharedSourcesPlugin's own header documents the leak.

Root-anchored patterns rather than bare globs: `*.o` would hide a file anywhere
in the tree, and these only ever appear beside Package.swift. Verified both
ways — the seven root spellings are ignored, the same extensions nested under
Sources/ are not.

No cleanup trap added to the build scripts. Neither compiles `P256K`: a
`-dry-run` plan for `-scheme Supabase` contains no `P256K`, `libsecp256k1` or
`SharedSourcesPlugin` entry, so a trap there would not fire on the real cause,
and an unconditional root-level `find -delete` for globs as generic as `*.d`
would remove untracked files the script never created.

13679 of 14542 relevant lines covered (94.07%)

605650.9 hits per line

Jobs
ID Job ID Ran Files Coverage
1 41106605598.1 194
94.07
GitHub Action Run
Source Files on build 41106605598