Skip to content

Conversation

@berkayoz
Copy link
Member

Description

What issue is this PR trying to solve?

Solution

A clear and concise description of how your changes address the above issue.

Issue

Include a link to the Github issue number if applicable.

Backport

Should this PR be backported? If so, to which release?

Checklist

  • PR title formatted as type: title
  • Covered by unit tests
  • Covered by integration tests
  • Documentation updated
  • CLA signed
  • Backport label added if necessary

If any item on the checklist is not complete, please provide justification why.

The PR title is expected to contain one of the following prefixes, following the
Conventional Commits specification:

  • 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

@berkayoz berkayoz force-pushed the KU-4355/lxd-storage-backend branch from c9c6194 to a1f50c1 Compare October 16, 2025 09:05
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