diff options
| author | Kubernetes Prow Robot <k8s-ci-robot@users.noreply.github.com> | 2022-01-30 23:30:24 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-01-30 23:30:24 -0800 |
| commit | 09fa4f3113db8b5832e221bf40af348c256e4b3c (patch) | |
| tree | 9fa6627da5457ec29ea885ab3b021f66339d8690 | |
| parent | 4f0cf1e20542f66694ca0a5f59d37cba3e17853b (diff) | |
| parent | 3da706ad235467d6d942379408eeebf6195701f2 (diff) | |
Merge pull request #6412 from alisondy/guide-fix-broken-link
Fix broken links to learn about sigs in the contributor guide
| -rw-r--r-- | contributors/guide/contributing.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/contributors/guide/contributing.md b/contributors/guide/contributing.md index 2b74f4f1..72eeffa5 100644 --- a/contributors/guide/contributing.md +++ b/contributors/guide/contributing.md @@ -33,7 +33,7 @@ For quick reference on contributor resources, we have a handy [contributor cheat ### Communication -It is best to contact your [SIG](#learn-about-sigs) for issues related to the SIG's topic. Your SIG will be able to help you much more quickly than a general question would. +It is best to contact your [SIG](first-contribution.md#learn-about-sigs) for issues related to the SIG's topic. Your SIG will be able to help you much more quickly than a general question would. For general questions and troubleshooting, use the [standard lines of communication](/communication/README.md) and work through the [troubleshooting guide](https://kubernetes.io/docs/tasks/debug-application-cluster/troubleshooting/). @@ -61,7 +61,7 @@ Refer to its [command reference documentation](https://go.k8s.io/bot-commands). Common new contributor PR issues are: * not having correctly signed the CLA ahead of your first PR. See the [CLA page](/CLA.md) for troubleshooting help, in some cases you might need to file a ticket with the CNCF to resolve a CLA problem. -* finding the right SIG or reviewer(s) for the PR (see [Code Review](#code-review) section) and following any SIG or repository specific contributing guidelines (see [Learn about SIGs](#learn-about-sigs) section) +* finding the right SIG or reviewer(s) for the PR (see [Code Review](#code-review) section) and following any SIG or repository specific contributing guidelines (see [Learn about SIGs](first-contribution.md#learn-about-sigs) section) * dealing with test cases which fail on your PR, unrelated to the changes you introduce (see [Test Flakes](/contributors/devel/sig-testing/flaky-tests.md)) * Not following [scalability good practices](scalability-good-practices.md) * Include mentions (like @person) and [keywords](https://help.github.com/en/articles/closing-issues-using-keywords) which could close the issue (like fixes #xxxx) in commit messages. |