diff options
| author | Ellen Körbes <ellenkorbes@gmail.com> | 2018-02-25 16:19:40 -0300 |
|---|---|---|
| committer | Ellen Körbes <ellenkorbes@gmail.com> | 2018-02-25 16:19:40 -0300 |
| commit | f9efbe89e8759a4f62a31a2c4dfe1c125728c3a3 (patch) | |
| tree | 50853d410cfc31e72bf4d025e7d79ef00bb166a7 /contributors/guide/README.md | |
| parent | 626c637b3344d3734df6091f1efd0652f2933da4 (diff) | |
CNI link
Diffstat (limited to 'contributors/guide/README.md')
| -rw-r--r-- | contributors/guide/README.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/guide/README.md b/contributors/guide/README.md index 45abeb2f..b3015329 100644 --- a/contributors/guide/README.md +++ b/contributors/guide/README.md @@ -101,7 +101,7 @@ For Pull Requests, the automatically assigned reviewer will add a SIG label if y For Issues, we are still working on a more automated workflow. Since SIGs do not directly map onto Kubernetes subrepositories, it may be difficult to find which SIG your contribution belongs in. Here is the [list of SIGs](/sig-list.md). Determine which is most likely related to your contribution. -*Example:* if you are filing a CNI issue (that's Container Networking Interface), you should choose the [Network SIG](http://git.k8s.io/community/sig-network). Add the SIG label in a comment like so: +*Example:* if you are filing a CNI issue (that's [Container Networking Interface](https://github.com/containernetworking/cni)), you should choose the [Network SIG](http://git.k8s.io/community/sig-network). Add the SIG label in a comment like so: ``` /sig network ``` |