master → main branch renaming

[sbrl]

Calling all maintainers of both clients and tldr alike!

The master branch has now been renamed to main.

Client authors

While a new mirror branch master that reflects main has been created, please update your clients if required to default to main instead of master. In the future the master mirror branch will be deleted.

Note though that it is RECOMMENDED that you download our tldr.zip instead of cloning this repository, as per our client specification if appropriate.

tldr maintainers

All existing PRs and branch protection rules have been updated.

Please watch out for new PRs that merge against master, as I have been unable to create a branch protection rule on master that doesn't also block GitHub Actions from pushing to it.

---

This discussion was created from the release `master` → `main` branch renaming.

[sbrl]

Hey there! I'm not sure what you're asking here?

[jxu]

This change by GitHub was IMO too breaking and has caused quite a bit of confusion for me. If I go to https://github.com/tldr-pages/tldr/tree/master, it says it is up to date with main. Yet in my local git repo, git checkout master shows only commits up to Feb 2020 and git pull or git reset does nothing. I must be misunderstanding something here.

[navarroaxel]

it's your responsibility keep your fork up to date. BTW actually you don't need to sync your fork, just use origin/master and push to jxu/ to create new PRs.

[jxu]

My fork master branch was up to date with git pulls, until the branch name change.

[navarroaxel]

🤔 git pull (read) only fetch changes to your working copy, doesn't update the fork itself, you need a push (write) for that.

[jxu]

Ok I think I synced everything with creating the upstream remote of the official repo. (I'm pretty sure I had this before but I'm not sure what happened)

[iridacea]

it's your responsibility keep your fork up to date. BTW actually you don't need to sync your fork, just use origin/master and push to jxu/ to create new PRs.

Just a note. That is true, but doing this way increases chances of conflict changes, and one would end up resolving that via Github's web-interface, instead of resolving it locally or even avoiding it.

[dgx-spark]

Hi there,

I am trying to install tldr pages with npm and pip in WSL Kali Linux and got this error.

Error: /mnt/c/Users/rsa/AppData/Roaming/npm/tldr: 11: exec: node: not found

[kbdharun]

It seems that there is an error with the executable in the specified path.

Have you tried updating or reinstalling npm?

I tried both the clients in Kali before it worked fine. (Not in WSL)

If npm is up to date, Try to reinstall the client by following the guide for our npm-client.

I would suggest you use our npm-client in Kali as pip dependencies are outdated sometimes in it.

Feel free to let me know if it works

[navarroaxel]

Looks like node is not available in the path, are you mounting a Windows filesystem on Linux? are you using nvm?