|
Ran
|
Jobs
2
|
Files
15
|
Run time
1min
|
Badge
README BADGES
|
push
github
📦 Fix `setuptools-scm` warnings on git archival (#55) Prior to this patch, `python -Im build` would emit warnings regarding `.git_archival.txt` having not been templated that look as follows: ```console $ python -Im build -vv 2>&1 | grep -i warni /tmp/build-env-m3vufmd9/lib/python3.14/site-packages/setuptools_scm/git.py:427: UserWarning: git archive did not support describe output warnings.warn("git archive did not support describe output") /tmp/build-env-m3vufmd9/lib/python3.14/site-packages/setuptools_scm/git.py:445: UserWarning: unprocessed git archival found (no export subst applied) warnings.warn("unprocessed git archival found (no export subst applied)") /tmp/build-env-m3vufmd9/lib/python3.14/site-packages/setuptools_scm/git.py:427: UserWarning: git archive did not support describe output warnings.warn("git archive did not support describe output") /tmp/build-env-m3vufmd9/lib/python3.14/site-packages/setuptools_scm/git.py:445: UserWarning: unprocessed git archival found (no export subst applied) warnings.warn("unprocessed git archival found (no export subst applied)") ``` This change addressed that by excluding said file from sdists produced from within Git checkouts so the file only exists when exported into an archive. `MANIFEST.in` itself is excluded due to a cascading warning its presence introduces while fixing the original one. ctx: pypa/pip-tools#2261 (comment) (cherry picked from commit cf16447bf)
3 of 6 branches covered (50.0%)
Branch coverage included in aggregate %.
1104 of 1116 relevant lines covered (98.92%)
5.92 hits per line
| ID | Job ID | Ran | Files | Coverage | |
|---|---|---|---|---|---|
| 1 | MyPy - 41334514037.1 | 45 |
98.66
|
GitHub Action Run | |
| 2 | MyPy - 41334514037.2 | 45 |
98.66
|
GitHub Action Run |
| Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line | Branch Hits | Branch Misses |
|---|