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

fix(core): adapt new database chip color scheme #8697

Merged

Conversation

pengx17
Copy link
Collaborator

@pengx17 pengx17 commented Nov 4, 2024

fix AF-1609

Copy link

graphite-app bot commented Nov 4, 2024

Your org has enabled the Graphite merge queue for merging into canary

Add the label “merge” to the PR and Graphite will automatically add it to the merge queue when it’s ready to merge. Or use the label “hotfix” to add to the merge queue as a hot fix.

You must have a Graphite account and log in to Graphite in order to use the merge queue. Sign up using this link.

Copy link
Collaborator Author

pengx17 commented Nov 4, 2024

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @pengx17 and the rest of your teammates on Graphite Graphite

@pengx17 pengx17 marked this pull request as ready for review November 4, 2024 13:45
@pengx17 pengx17 force-pushed the 11-04-fix_core_adapt_new_database_chip_color_scheme branch from 8b9492f to b640517 Compare November 4, 2024 13:46
Copy link

nx-cloud bot commented Nov 4, 2024

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 684b676. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution


✅ Successfully ran 1 target

Sent with 💌 from NxCloud.

Copy link

codecov bot commented Nov 4, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 70.06%. Comparing base (aae71a2) to head (684b676).
Report is 1 commits behind head on canary.

Additional details and impacted files
@@           Coverage Diff           @@
##           canary    #8697   +/-   ##
=======================================
  Coverage   70.06%   70.06%           
=======================================
  Files         546      546           
  Lines       33809    33809           
  Branches     3055     3055           
=======================================
  Hits        23689    23689           
  Misses       9759     9759           
  Partials      361      361           
Flag Coverage Δ
server-test 77.12% <ø> (ø)
unittest 44.98% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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

@pengx17 pengx17 force-pushed the 11-04-fix_core_adapt_new_database_chip_color_scheme branch from b640517 to c3f00f6 Compare November 5, 2024 03:09
Copy link

graphite-app bot commented Nov 5, 2024

Merge activity

  • Nov 5, 2:06 AM EST: A user added this pull request to the Graphite merge queue.
  • Nov 5, 3:17 AM EST: The Graphite merge queue couldn't merge this PR because it was not satisfying all requirements (Failed CI: '3, 2, 1 Launch', 'E2E Mobile Test (2)').
  • Nov 5, 3:30 AM EST: A user added this pull request to the Graphite merge queue.
  • Nov 5, 3:48 AM EST: A user merged this pull request with the Graphite merge queue.

forehalo pushed a commit that referenced this pull request Nov 5, 2024
@forehalo forehalo force-pushed the 11-04-fix_core_adapt_new_database_chip_color_scheme branch from c3f00f6 to 4c60cf6 Compare November 5, 2024 08:02
@pengx17 pengx17 force-pushed the 11-04-fix_core_adapt_new_database_chip_color_scheme branch from 4c60cf6 to 684b676 Compare November 5, 2024 08:34
@graphite-app graphite-app bot merged commit 684b676 into canary Nov 5, 2024
46 checks passed
@graphite-app graphite-app bot deleted the 11-04-fix_core_adapt_new_database_chip_color_scheme branch November 5, 2024 08:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants