summaryrefslogtreecommitdiff
path: root/contributors
diff options
context:
space:
mode:
authoramolmote <amolmote201@gmail.com>2022-09-11 08:59:36 +0530
committeramolmote <amolmote201@gmail.com>2022-09-11 08:59:36 +0530
commit4feca6b6e71304e1eed610c1e475e2d38c698ce5 (patch)
treeb9ac15077c45cbacaa1516b00899ebe5c3a9a514 /contributors
parenta08307d29b5a79b64df4ddd1ed1102a4e70e0e77 (diff)
updated contributors/guide/pull-requests.md
Signed-off-by: amolmote <amolmote201@gmail.com>
Diffstat (limited to 'contributors')
-rw-r--r--contributors/guide/pull-requests.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/guide/pull-requests.md b/contributors/guide/pull-requests.md
index 242e0bc9..e666c62c 100644
--- a/contributors/guide/pull-requests.md
+++ b/contributors/guide/pull-requests.md
@@ -178,7 +178,7 @@ Are you willing to bet a few days or weeks of work on it?
It's better to get confirmation beforehand.
-When you want to make a large or otherwise significant change, you should follow the [Kubernetes Enhancement Proposal process](https://git.k8s.io/enhancements/keps/0001-kubernetes-enhancement-proposal-process.md).
+When you want to make a large or otherwise significant change, you should follow the [Kubernetes Enhancement Proposal process](https://github.com/kubernetes/enhancements/blob/master/keps/sig-architecture/0000-kep-process/README.md).
Even for small changes, it is often a good idea to gather feedback on an issue you filed, or even simply ask in the appropriate SIG's Slack channel to invite discussion and feedback from code owners.
Here's a [list of SIGs](/sig-list.md), this includes their public meetings.