Skip to content

chore: update submodule with key value pair changes #165

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

Merged
merged 2 commits into from
Oct 31, 2022

Conversation

GurtejSohi
Copy link
Contributor

Description

Brings in the key-value pair added in the submodule - hypertrace/hypertrace-core-graphql#117

@GurtejSohi GurtejSohi requested a review from a team as a code owner October 31, 2022 06:04
@GurtejSohi GurtejSohi enabled auto-merge (squash) October 31, 2022 06:04
@codecov
Copy link

codecov bot commented Oct 31, 2022

Codecov Report

Merging #165 (1ea69cb) into main (0d0771f) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               main     #165   +/-   ##
=========================================
  Coverage     22.84%   22.84%           
  Complexity       75       75           
=========================================
  Files            65       65           
  Lines          1742     1742           
  Branches         53       53           
=========================================
  Hits            398      398           
  Misses         1335     1335           
  Partials          9        9           
Flag Coverage Δ
unit 22.84% <ø> (ø)

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

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@github-actions
Copy link

Test Results

25 tests  ±0   25 ✔️ ±0   24s ⏱️ +9s
11 suites ±0     0 💤 ±0 
11 files   ±0     0 ±0 

Results for commit 1ea69cb. ± Comparison against base commit 0d0771f.

@GurtejSohi GurtejSohi merged commit 89a0377 into main Oct 31, 2022
@GurtejSohi GurtejSohi deleted the update-submodule-with-kv-pair branch October 31, 2022 13:04
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