Closed fcollonval closed 1 year ago
@meeseeksdev please backport to 3.x
Owee, I'm MrMeeseeks, Look at me.
There seem to be a conflict, please backport manually. Here are approximate instructions:
git checkout 3.x
git pull
Cherry pick the first parent branch of the this PR on top of the older branch:
git cherry-pick -x -m1 e8dedca3690c3b1d0812d18bc23c9febb24cd925
You will likely have some merge/cherry-pick conflict here, fix them and commit:
git commit -am 'Backport PR #50: Add factory token for jupytext customization'
git push YOURFORK 3.x:auto-backport-of-pr-50-on-3.x
"Backport PR #50 on branch 3.x (Add factory token for jupytext customization)"
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.
Jupytext PR is up: https://github.com/mwouts/jupytext/pull/1126
This:
Fixes partly https://github.com/jupyterlab-contrib/rise/issues/17#issuecomment-1699442075 cc @nthiery
This will need to be backported on 3.x and then a PR will be required on jupytext itself (code already written and tested https://github.com/fcollonval/jupytext/tree/ft/support-lab-rise).