Fixes the command for switching to getting-started dir after cloning

[syed-awais-ali]

Relates to in case of new feature, this should point to issue/(s) which describes the feature

Fixes #<issue number>. in case of a bug fix, this should point to a bug and any other related issue(s)

Should merge before : list any PRs that depend on this PR

Should merge after : list any PRs that are prerequisites to this PR

Description

User facing changes

Write n/a if not output or log lines changed and no behavior is changed

Before

If log/output changes: Paste the current relevant skaffold output
If behavior changes: describe succinctly the current behavior

After

If log/output changes: Paste skaffold output after your change
If behavior changes: describe succinctly the behavior after your change

Next PRs.

Submitter Checklist

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

• Includes unit tests
• Mentions any output changes.
• Adds documentation as needed: user docs, YAML reference, CLI reference.
• Adds integration tests if needed.

Reviewer Notes

• The code flow looks good.
• Unit test added.
• User facing changes look good.

Release Notes

Examples of user facing changes:
- Skaffold config changes like
  e.g. "Add buildArgs to `Kustomize` deployer skaffold config."
- Bug fixes
  e.g. "Improve skaffold init behavior when tags are used in manifests"
- Any changes in skaffold behavior
  e.g. "Artifact caching is turned on by default."

[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.

[codecov]

Codecov Report

Merging #3574 into master will decrease coverage by 0.01%.
The diff coverage is n/a.

Impacted Files	Coverage Δ
...affold/kubernetes/portforward/kubectl_forwarder.go	65.85% <0%> (-2.44%)	⬇️

[syed-awais-ali]

@googlebot I signed it

[googlebot]

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.