Skip to content

configs-to-gcsfuse#4726

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

configs-to-gcsfuse#4726
PranjalC100 wants to merge 1 commit into
masterfrom
send-gcsfuse-config-to-bigstore

Conversation

@PranjalC100
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
Copy link
Copy Markdown

github-actions Bot commented May 25, 2026

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 "configs-to-gcsfuse". 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

@PranjalC100 PranjalC100 changed the title draft changes configs-to-gcsfuse May 25, 2026
@PranjalC100 PranjalC100 force-pushed the send-gcsfuse-config-to-bigstore branch 2 times, most recently from 893162e to 42ba7a8 Compare May 29, 2026 06:46
@PranjalC100 PranjalC100 force-pushed the send-gcsfuse-config-to-bigstore branch from 42ba7a8 to 271d035 Compare May 29, 2026 07:32
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.

1 participant