Skip to content

Conversation

@orcsin
Copy link

@orcsin orcsin commented Dec 1, 2025

Description

Update Velero documentation

Fixes #319

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Improvement

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.

Checklist

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • Pull Request contain one commit. I squash my commits.

Screenshots (if appropriate)

Additional context

@orcsin orcsin requested a review from a team as a code owner December 1, 2025 08:43
@orcsin orcsin force-pushed the main branch 2 times, most recently from 273a070 to 8bab089 Compare December 2, 2025 20:50
@orcsin orcsin changed the title docs: Update Velero documentation (#371) docs: Update Velero documentation (#319) Dec 4, 2025
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.

Update Velero documentation

3 participants