Skip to content

ci: explore using docker caching #1751

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

Closed
wants to merge 3 commits into from

Conversation

G-Rath
Copy link
Collaborator

@G-Rath G-Rath commented Mar 26, 2025

No description provided.

@G-Rath G-Rath force-pushed the ci/use-docker-cache branch from 382ca89 to 31a3f44 Compare March 26, 2025 02:28
@G-Rath G-Rath force-pushed the ci/use-docker-cache branch from 31a3f44 to f83ecbe Compare March 26, 2025 18:33
@codecov-commenter
Copy link

codecov-commenter commented Mar 26, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 64.85%. Comparing base (46632c0) to head (e3d45e0).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1751   +/-   ##
=======================================
  Coverage   64.85%   64.85%           
=======================================
  Files         157      157           
  Lines       15839    15839           
=======================================
  Hits        10272    10272           
  Misses       4893     4893           
  Partials      674      674           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@G-Rath G-Rath closed this May 21, 2025
@G-Rath G-Rath deleted the ci/use-docker-cache branch May 21, 2025 02:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants