Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Report code coverage to Codacy #950

Merged
merged 2 commits into from Mar 15, 2024
Merged

Report code coverage to Codacy #950

merged 2 commits into from Mar 15, 2024

Conversation

paulelliott
Copy link
Member

@paulelliott paulelliott commented Mar 14, 2024

📦 Published PR as canary version: 11.1.1--canary.950.8339507431.0

✨ Test out this PR locally via:

npm install chromatic@11.1.1--canary.950.8339507431.0
# or 
yarn add chromatic@11.1.1--canary.950.8339507431.0

Copy link

codacy-production bot commented Mar 14, 2024

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation Diff coverage
Report missing for 06ab0e51
Coverage variation details
Coverable lines Covered lines Coverage
Common ancestor commit (06ab0e5) Report Missing Report Missing Report Missing
Head commit (f85babd) 8431 6635 78.70%

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details
Coverable lines Covered lines Diff coverage
Pull request (#950) 0 0 ∅ (not applicable)

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

You may notice some variations in coverage metrics with the latest Coverage engine update. For more details, visit the documentation

Footnotes

  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.

@paulelliott
Copy link
Member Author

image

@paulelliott paulelliott added internal Classification: Changes only affect the internal API dependencies Classification: Update one or more dependencies version tests Classification: Add or improve existing tests and removed internal Classification: Changes only affect the internal API dependencies Classification: Update one or more dependencies version labels Mar 14, 2024
@paulelliott paulelliott self-assigned this Mar 14, 2024
Copy link
Member

@thafryer thafryer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks Good!

@paulelliott paulelliott added skip-release Auto: Preserve the current version when merged patch Auto: Increment the patch version when merged and removed skip-release Auto: Preserve the current version when merged labels Mar 15, 2024
@paulelliott paulelliott added this pull request to the merge queue Mar 15, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Mar 15, 2024
@paulelliott paulelliott added this pull request to the merge queue Mar 15, 2024
Merged via the queue into main with commit 4e0c1a7 Mar 15, 2024
30 of 40 checks passed
@paulelliott paulelliott deleted the code-coverage branch March 15, 2024 15:10
@ghengeveld
Copy link
Member

🚀 PR was released in v11.1.0 🚀

@ghengeveld ghengeveld added the released Verdict: This issue/pull request has been released label Mar 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
patch Auto: Increment the patch version when merged released Verdict: This issue/pull request has been released skip-release Auto: Preserve the current version when merged tests Classification: Add or improve existing tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants