Thanks for making a pull request to jupyterlab!
To try out this branch on binder, follow this link:

@meeseeksdev please backport to 4.0.x

@meeseeksdev please backport to 3.6.x

Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

1. Checkout backport branch and update it.

git checkout 3.6.x
git pull

2. Cherry pick the first parent branch of the this PR on top of the older branch:

git cherry-pick -x -m1 64fca7b29c9bb7c6470e324fc9982873ebe7e474

3. You will likely have some merge/cherry-pick conflict here, fix them and commit:

git commit -am 'Backport PR #14861: Fix broken link to security model'

4. Push to a named branch:

git push YOURFORK 3.6.x:auto-backport-of-pr-14861-on-3.6.x

5. Create a PR against branch 3.6.x, I would have named this PR:

"Backport PR #14861 on branch 3.6.x (Fix broken link to security model)"

And apply the correct labels and milestones.

Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon!

Remember to remove the Still Needs Manual Backport label once the PR gets merged.

If these instructions are inaccurate, feel free to suggest an improvement.

No need to backport as that documentation was added in 4.0.0