mirror of
https://github.com/vmware-tanzu/velero.git
synced 2026-10-21 22:03:09 +00:00
docs: fix contributor and maintainer guidance links (#10617)
e2e-test-kind.yaml / extract (push) Failing after 13s
Run the E2E test on kind / get-go-version (push) Failing after 17s
Run the E2E test on kind / build (push) Skipped
Run the E2E test on kind / setup-test-matrix (push) Failing after 4s
Run the E2E test on kind / run-e2e-test (push) Skipped
push.yml / extract (push) Failing after 6s
Scorecard supply-chain security / Scorecard analysis (push) Skipped
Main CI / get-go-version (push) Failing after 7s
Main CI / Build (push) Skipped
e2e-test-kind.yaml / extract (push) Failing after 13s
Run the E2E test on kind / get-go-version (push) Failing after 17s
Run the E2E test on kind / build (push) Skipped
Run the E2E test on kind / setup-test-matrix (push) Failing after 4s
Run the E2E test on kind / run-e2e-test (push) Skipped
push.yml / extract (push) Failing after 6s
Scorecard supply-chain security / Scorecard analysis (push) Skipped
Main CI / get-go-version (push) Failing after 7s
Main CI / Build (push) Skipped
* docs: fix contributor and maintainer guidance links Signed-off-by: xinjun.jiang <xinjun.jiang@daocloud.io> * docs: add contributor guidance changelog Record the contributor and maintainer documentation link corrections in the release notes. Signed-off-by: jxj <xinjun.jiang@daocloud.io> --------- Signed-off-by: xinjun.jiang <xinjun.jiang@daocloud.io> Signed-off-by: jxj <xinjun.jiang@daocloud.io>
This commit is contained in:
+1
-1
@@ -4,7 +4,7 @@
|
||||
|
||||
## Maintainers
|
||||
|
||||
All maintainers share collective responsibility for the entire Velero project. There are no siloed, per-area owners: every maintainer is a final reviewer of pull requests across the codebase, and code ownership is assigned to the maintainer group as a whole (see [CODEOWNERS](https://github.com/velero-io/velero/blob/main/CODEOWNERS)). Maintainers review PRs, ensure code quality, triage issues, fix bugs, and perform release and maintenance tasks across all components.
|
||||
All maintainers share collective responsibility for the entire Velero project. There are no siloed, per-area owners: every maintainer is a final reviewer of pull requests across the codebase, and code ownership is assigned to the maintainer group as a whole (see [CODEOWNERS](https://github.com/velero-io/velero/blob/main/.github/CODEOWNERS)). Maintainers review PRs, ensure code quality, triage issues, fix bugs, and perform release and maintenance tasks across all components.
|
||||
|
||||
| Maintainer | GitHub ID | Affiliation |
|
||||
|---------------------|---------------------------------------------------------------|--------------------------------------------------|
|
||||
|
||||
@@ -0,0 +1 @@
|
||||
Fixed broken links to contributor guidance and code ownership in the documentation.
|
||||
@@ -28,7 +28,7 @@ Please browse our list of resources, including a playlist of past online communi
|
||||
|
||||
If you are ready to jump in and test, add code, or help with documentation, please use the navigation on the left under `Contribute`.
|
||||
|
||||
[1]: https://github.com/velero-io/velero/blob/main/CODE_OF_CONDUCT.md
|
||||
[2]: https://github.com/velero-io/velero/blob/main/CONTRIBUTING.md
|
||||
[1]: https://github.com/velero-io/.github/blob/main/CODE_OF_CONDUCT.md
|
||||
[2]: https://github.com/velero-io/.github/blob/main/CONTRIBUTING.md
|
||||
[3]: https://github.com/velero-io/velero/blob/main/.github/ISSUE_TEMPLATE/feature-enhancement-request.md
|
||||
[4]: https://github.com/velero-io/velero/blob/main/.github/ISSUE_TEMPLATE/bug_report.md
|
||||
|
||||
Reference in New Issue
Block a user