Skip to content

json gzip try config useragent#4774

Draft
PranjalC100 wants to merge 1 commit into
masterfrom
send-gcsfuse-config-to-bigstore-json
Draft

json gzip try config useragent#4774
PranjalC100 wants to merge 1 commit into
masterfrom
send-gcsfuse-config-to-bigstore-json

Conversation

@PranjalC100

@PranjalC100 PranjalC100 commented Jun 10, 2026

Copy link
Copy Markdown
Member

Please ensure your PR title follows the format:

type(scope): subject

Example:
feat(api): add user login endpoint

Available types:

  • feat: A new feature
  • fix: A bug fix
  • docs: Documentation only changes
  • style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
  • refactor: A code change that neither fixes a bug nor adds a feature
  • perf: A code change that improves performance
  • test: Adding missing tests or correcting existing tests
  • build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
  • ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
  • chore: Other changes that don't modify src or test files
  • revert: Reverts a previous commit

Description

Link to the issue in case of a bug fix.

Testing details

  1. Manual - NA
  2. Unit tests - NA
  3. Integration tests - NA

Any backward incompatible change? If so, please explain.

@github-actions

github-actions Bot commented Jun 10, 2026

Copy link
Copy Markdown

Hey there and thank you for opening this pull request! 👋🏼

We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.

Details:

No release type found in pull request title "json gzip try config useragent". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit

@codecov

codecov Bot commented Jun 10, 2026

Copy link
Copy Markdown

Codecov Report

❌ Patch coverage is 74.07407% with 21 lines in your changes missing coverage. Please review.
✅ Project coverage is 83.65%. Comparing base (d47010c) to head (fcdafb0).

Files with missing lines Patch % Lines
cfg/config_json.go 77.14% 4 Missing and 4 partials ⚠️
cmd/legacy_main.go 65.21% 6 Missing and 2 partials ⚠️
cfg/types.go 81.25% 2 Missing and 1 partial ⚠️
internal/storage/storage_handle.go 71.42% 1 Missing and 1 partial ⚠️
Additional details and impacted files 
@@            Coverage Diff             @@
##           master    #4774      +/-   ##
==========================================
- Coverage   83.67%   83.65%   -0.03%     
==========================================
  Files         168      169       +1     
  Lines       20784    20857      +73     
==========================================
+ Hits        17392    17447      +55     
- Misses       2742     2752      +10     
- Partials      650      658       +8
Flag Coverage Δ
unittests 83.65% <74.07%> (-0.03%) ⬇️

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

☔ View full report in Codecov by Harness.
📢 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@meet2mky meet2mky Awaiting requested review from meet2mky meet2mky will be requested when the pull request is marked ready for review meet2mky is a code owner

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@PranjalC100