docs: fix broken anchor links in main docs (#10638)
Run the E2E test on kind / setup-test-matrix (push) Failing after 3s
e2e-test-kind.yaml / extract (push) Failing after 8s
Run the E2E test on kind / get-go-version (push) Failing after 9s
Run the E2E test on kind / build (push) Skipped
Run the E2E test on kind / run-e2e-test (push) Skipped
push.yml / extract (push) Failing after 7s
Main CI / get-go-version (push) Failing after 8s
Main CI / Build (push) Skipped
Scorecard supply-chain security / Scorecard analysis (push) Skipped

* docs: fix broken anchor links in main docs

- csi-snapshot-data-movement: link to restore-reference.md#changing-pvpvc-storage-classes
  (Hugo drops the slash from the 'Changing PV/PVC Storage Classes' heading id)
- customize-installation: the Homebrew install section is in basic-install.md,
  not on this page
- repository-maintenance: backup-repository-configuration.md has no
  #full-maintenance-interval-customization heading; link to the page

Signed-off-by: Satvik Mishra <Satvikmishra.ipu146183@maims.ac.in>

* Add changelog for #10638

Signed-off-by: Satvik Mishra <Satvikmishra.ipu146183@maims.ac.in>

---------

Signed-off-by: Satvik Mishra <Satvikmishra.ipu146183@maims.ac.in>
This commit is contained in:
Satvik Mishra
2026-10-13 00:46:10 -04:00
committed by GitHub
parent 0d28bab85e
commit c111008912
4 changed files with 4 additions and 3 deletions
@@ -0,0 +1 @@
Fix broken anchor links in the main docs
@@ -650,7 +650,7 @@ Sometimes, `RestorePVC` needs to be configured to increase the performance of re
[7]: https://docs.microsoft.com/en-us/azure/aks/azure-files-dynamic-pv
[8]: api-types/backupstoragelocation.md
[9]: supported-providers.md
[10]: restore-reference.md#changing-pv/pvc-Storage-Classes
[10]: restore-reference.md#changing-pvpvc-storage-classes
[11]: data-movement-pod-resource-configuration.md
[12]: performance-guidance.md
[13]: https://kubernetes.io/docs/concepts/workloads/pods/pod-qos/
@@ -475,7 +475,7 @@ You now have to ensure that the velero completion script gets sourced in all you
echo 'complete -F __start_velero v' >>~/.bashrc
```
- If you installed velero with Homebrew (as explained [above](#install-with-homebrew-on-macos)), then the velero completion script should already be in `/usr/local/etc/bash_completion.d/velero`. In that case, you don't need to do anything.
- If you installed velero with Homebrew (as explained in [Basic Install](basic-install.md#option-1-macos---homebrew)), then the velero completion script should already be in `/usr/local/etc/bash_completion.d/velero`. In that case, you don't need to do anything.
> The Homebrew installation of bash-completion v2 sources all the files in the `BASH_COMPLETION_COMPAT_DIR` directory, that's why the latter two methods work.
@@ -264,7 +264,7 @@ Note that `podLabels` and `podAnnotations` are only read from the global configu
[1]: velero-install.md#usage
[2]: node-agent-concurrency.md
[3]: backup-repository-configuration.md#full-maintenance-interval-customization
[3]: backup-repository-configuration.md
[4]: https://github.com/velero-io/velero/blob/d5a2e7e6b9512e8ba52ec269ed5ce9a0fa23548c/pkg/util/third_party.go#L19-L21
[5]: https://github.com/velero-io/velero/blob/d5a2e7e6b9512e8ba52ec269ed5ce9a0fa23548c/pkg/util/third_party.go#L23-L25
[6]: https://github.com/velero-io/velero/blob/d5a2e7e6b9512e8ba52ec269ed5ce9a0fa23548c/pkg/util/third_party.go#L27-L30