Finish the rename of yarn ls to yarn list.

[markstos]

• Update yarn list command docs #356 did not create redirect
• Rename to list.md and change "ls" to "list" #334 duplicated some work already done in 📝 ls → list #333 also did not update
  all necessary files.

Once this is merged, both #334 and #356 can be closed.

[Daniel15]

Maybe do this for every language, and use a relative URI so it works properly at the preview URL:

/:language/docs/cli/ls   /:language/docs/cli/list 301

Some test cases:

• https://deploy-preview-377--yarnpkg.netlify.com/en/docs/cli/ls --> should redirect to https://deploy-preview-377--yarnpkg.netlify.com/en/docs/cli/list
• https://deploy-preview-377--yarnpkg.netlify.com/fr/docs/cli/ls
• https://deploy-preview-377--yarnpkg.netlify.com/pt-BR/docs/cli/ls

(you can get this preview URL from the bottom of the pull request, where it says "deploy/netlify — Deploy preview ready!")

[marcusmolchany]

Lines 11 and 13 of lang/en/docs/cli/global.md have occurrences of ls that should be list

_data/i18n/en.yml must be changed as noted in #356

_data/guides.yml has occurrences of ls

I think #277 has all the changes but has a merge conflict

[markstos]

@marcusmolchany :

Lines 11 and 13 of lang/en/docs/cli/global.md have occurrences of ls that should be list

No, yarn global ls has not been renamed, so these docs should not be updated at this time. Arguably, yarn global ls should be renamed as well, but it hasn't been.

_data/i18n/en.yml must be changed

This PR did change this file as noted in #356. If there's anothe change to make to this file, I'm not sure what you are referring to.

_data/guides.yml has occurrences of ls

Those are just internal IDs, not user-facing docs

_data/guides.yml has occurrences of ls

Thanks. I missed one there. Corrected.

[markstos]

@Daniel15 I've now done a force push of my proposed fix which addresses all open feedback.

If this is accepted, 3 open related PRs can be closed as well that had all partially addressed what needed to be fixed.

[bestander]

@markstos, sorry for a delay.
What is the status of this one? Good to merge?
Let's rebase and merge if it is.

[markstos]

@bestander I'm aware no outstanding feedback to be addressed on this PR, so it seems good to merge to me. I've now rebased it onto master.

[bestander]

Thanks, @markstos!