diff --git a/contributors/devel/README.md b/contributors/devel/README.md index 47dd9db72..98863a54c 100644 --- a/contributors/devel/README.md +++ b/contributors/devel/README.md @@ -17,7 +17,7 @@ Guide](http://kubernetes.io/docs/admin/). * **GitHub Issues** ([issues.md](issues.md)): How incoming issues are triaged. -* **Pull Request Process** ([pull-requests.md](pull-requests.md)): When and why pull requests are closed. +* **Pull Request Process** ([/contributors/guide/pull-requests.md](/contributors/guide/pull-requests.md)): When and why pull requests are closed. * **Getting Recent Builds** ([getting-builds.md](getting-builds.md)): How to get recent builds including the latest builds that pass CI. diff --git a/contributors/devel/cherry-picks.md b/contributors/devel/cherry-picks.md index 232b2a0b1..7a049149a 100644 --- a/contributors/devel/cherry-picks.md +++ b/contributors/devel/cherry-picks.md @@ -6,7 +6,7 @@ depending on the point in the release cycle. ## Propose a Cherry Pick -1. Cherrypicks are [managed with labels and milestones](pull-requests.md#write-release-notes-if-needed) +1. Cherrypicks are [managed with labels and milestones](/contributors/guide/release-notes.md) 1. To get a PR merged to the release branch, first ensure the following labels are on the original **master** branch PR: * The milestone for the branch that you want to cherry-pick to (e.g. v1.7 if you want to backport your change in 1.7 branch) diff --git a/contributors/devel/faster_reviews.md b/contributors/devel/faster_reviews.md index 37de43cb3..66fe9ab0c 100644 --- a/contributors/devel/faster_reviews.md +++ b/contributors/devel/faster_reviews.md @@ -1,3 +1,3 @@ # How to get faster PR reviews -Merged with the [pull requests doc](pull-requests.md#best-practices-for-faster-reviews). +Merged with the [pull requests doc](/contributors/guide/pull-requests.md#best-practices-for-faster-reviews). diff --git a/contributors/guide/community-expectations.md b/contributors/guide/community-expectations.md index fa4f951fc..ccff6441a 100644 --- a/contributors/guide/community-expectations.md +++ b/contributors/guide/community-expectations.md @@ -22,7 +22,7 @@ As a community we believe in the value of code review for all contributions. Code review increases both the quality and readability of our codebase, which in turn produces high quality software. -See the [pull request documentation](/contributors/devel/pull-requests.md) for more information +See the [pull request documentation](/contributors/guide/pull-requests.md) for more information on code review. Consequently, as a community we expect that all active participants in the diff --git a/contributors/guide/github-workflow.md b/contributors/guide/github-workflow.md index c96e4e7d4..a8c4eae68 100644 --- a/contributors/guide/github-workflow.md +++ b/contributors/guide/github-workflow.md @@ -179,7 +179,7 @@ git push -f ${your_remote_name} myfeature 1. Visit your fork at https://github.com/$user/kubernetes 2. Click the `Compare & Pull Request` button next to your `myfeature` branch. -3. Check out the pull request [process](/contributors/devel/pull-requests.md) for more details and +3. Check out the pull request [process](/contributors/guide/pull-requests.md) for more details and advice. _If you have upstream write access_, please refrain from using the GitHub UI for