doc(dev): never use "here" as a link

[docwhat]

Tiny change because you should never use "here" as a link.

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[tekton-robot]

Hi @docwhat. Thanks for your PR.

I'm waiting for a tektoncd member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[ghost]

/ok-to-test

[bobcatfish]

Thanks for this @docwhat ! Looks like you need to sign the CLA before we can merge 🙏

Side note: @spomorski is working on a style guide for us so we can stop doing stuff like this :D

[bobcatfish]

oooo much clearer!

[tualeron]

Great idea - just added this to our style guide. :)

…

On Fri, Jan 17, 2020 at 2:13 PM Christie Wilson ***@***.***> wrote: ***@***.**** commented on this pull request. Thanks for this @docwhat <https://github.com/docwhat> ! Looks like you need to sign the CLA before we can merge 🙏 Side note: @spomorski <https://github.com/spomorski> is working on a style guide for us so we can stop doing stuff like this :D ------------------------------ In docs/developers/README.md <#1892 (comment)>: > @@ -19,7 +19,7 @@ on path `/pvc` by PipelineRun. Another alternatives is to use a GCS storage or S3 bucket to share the artifacts. This can be configured using a ConfigMap with the name `config-artifact-bucket`. -See [here](../install.md#how-are-resources-shared-between-tasks) for configuration details. +See the [installation docs](../install.md#how-are-resources-shared-between-tasks) for configuration details. oooo much clearer! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1892?email_source=notifications&email_token=AG3UR4RQ2WSRFLG2HVUQF4TQ6H7NVA5CNFSM4KIJ6N62YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCSGQEKY#pullrequestreview-344785451>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AG3UR4S5ZF6SYBAQH3LEHR3Q6H7NVANCNFSM4KIJ6N6Q> .

[docwhat]

@googlebot I signed it!
/test pull-tekton-pipeline-build-tests

[googlebot]

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

[vdemeester]

/lgtm

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vdemeester

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [vdemeester]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment