Closed jmhobbs closed 1 month ago
Coverage variation | Diff coverage |
---|---|
:white_check_mark: +0.07% (target: -1.00%) | :white_check_mark: 85.00% (target: 80.00%) |
Codacy stopped sending the deprecated coverage status on June 5th, 2024. Learn more
📦 Package Size: 5264 KB ✅ Compared to main: -4 KB 9ae51185d550eba0d8c12b8045b0f6a83c5f5903 (5268 KB)
@winkerVSbecks is there a better link I should use for this? I found https://www.chromatic.com/docs/custom-ci-provider/#overriding-chromatics-branch-detection but it does not mention CHROMATIC_BRANCH
or CHROMATIC_SLUG
on there.
@jmhobbs We could add an FAQ for precisely this scenario and link to that. wdty?
@jmhobbs We could add an FAQ for precisely this scenario and link to that. wdty?
Absolutely! I'll put this on hold for now until that is available.
@jmhobbs FAQ link that you can use instead: https://www.chromatic.com/docs/faq/override-branch-name/
Coverage variation | Diff coverage |
---|---|
Report missing for 9ae51185d550eba0d8c12b8045b0f6a83c5f5903[^1] | :white_check_mark: 84.21% (target: 80.00%) |
Codacy stopped sending the deprecated coverage status on June 5th, 2024. Learn more [^1]: Codacy didn't receive coverage data for the commit, or there was an error processing the received data. Check your integration for errors and validate that your coverage setup is correct.
:rocket: PR was released in v11.13.0
:rocket:
Sometimes our automatic CI detection lands us with an
undefined:<branch>
value, which is not correct.This strips that from branch values (unless explicitly set), and prints a warning message so users can possibly switch to
CHROMATIC_BRANCH
andCHROMATIC_SLUG
Also upgrades
env-ci
to detect more CI builders and hopefully avoid this situation in the first place.📦 Published PR as canary version:
11.13.1--canary.1101.11444008898.0
:sparkles: Test out this PR locally via: ```bash npm install chromatic@11.13.1--canary.1101.11444008898.0 # or yarn add chromatic@11.13.1--canary.1101.11444008898.0 ```