Fix typo in entrypoint folder

[ywluogg]

Changes

Fix typo in entrypoint folder

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

• Includes tests (if functionality changed/added)
• Includes docs (if user facing)
• Commit messages follow commit message best practices
• Release notes block has been filled in or deleted (only if no user facing changes)

See the contribution guide for more details.

Double check this list of stuff that's easy to miss:

• If you are adding a new binary/image to the cmd dir, please update
  the release Task to build and release this image.

Reviewer Notes

If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.

Release Notes

NONE

[tekton-robot]

Hi @ywluogg. 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.

[imjasonh]

Hey Yawen, thanks for the fix! The change looks good, there's just a couple things we need to do before we can merge this:

• Add a release notes section. In this case, since there are no changes to report in the release notes, I've just edited your PR description to add a release-note block.

• Squash your commits, so that your three commits become one single commit associated with this PR. To do this from your terminal, in the branch where you're making this change, see the "Squashing Commits" section of https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History

Let me know if you have any trouble and I can try to help in either case.

[imjasonh]

/ok-to-test

[imjasonh]

Oh we'll also want a more descriptive PR title than "Typo" -- your change description in the PR body ("Fix typo in entrypoint folder") would make a good PR title.

(This is actually also related to commit squashing -- when a PR includes multiple changes GitHub chooses the branch name for the PR title, which tends to be pretty non-descriptive. When there's only one squashed change, GitHub chooses that commit description for the PR title, which is usually much better)

[ywluogg]

Thanks for the comment. Edited the commit based on them

[imjasonh]

/kind documentation

[imjasonh]

/lgtm

[popcor255]

/lgtm
/cc @chmouel

Edit: I thought this was the catalog repo. 😝 🤦

[chmouel]

/lgtm

Looking Good! 🤙🏽

[chmouel]

/test check-pr-has-kind-label

[ywluogg]

I still have check-pr-has-kind-label marked as yellow but it already has a kind tag.

[ywluogg]

My checks were stuck, so I tried pushing a empty commit to re-try the checks to see if it fixes it.

[chmouel]

/lgtm

[ywluogg]

/assign @imjasonh

[imjasonh]

/approve

🎉

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ImJasonH

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 [ImJasonH]

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