search

jupyterlite / xeus-python-kernel

xeus-python in JupyterLite
https://xeus-python-kernel.readthedocs.io
BSD 3-Clause "New" or "Revised" License
30 stars 19 forks source link

Align repo with the extension template #168

Closed jtpio closed 9 months ago

jtpio commented 9 months ago

Align the repo with the extension template: https://github.com/jupyterlab/extension-template

This will ease maintenance over time.

It also migrates to using hatch instead of the deprecated jupyter-packaging.

It should also fix the current malformed version in package.json:

https://github.com/jupyterlite/xeus-python-kernel/blob/ee180add4582dbd6c177d59b29f63f420f87de54/package.json#L3

github-actions[bot] commented 9 months ago

lite-badge :point_left: Try it on ReadTheDocs

jtpio commented 9 months ago

Looking fine on ReadTheDocs:

image

jtpio commented 9 months ago

Also looking fine testing with the releaser assets locally:

image

martinRenou commented 7 months ago

meeseeksdev backport to 0.x

lumberbot-app[bot] commented 7 months ago

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 0.x
git pull

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

    git cherry-pick -x -m1 96aea3e341db3077cdebb749993606b66086f5c7

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

git commit -am 'Backport PR #168: Align repo with the extension template'
  1. Push to a named branch:
git push YOURFORK 0.x:auto-backport-of-pr-168-on-0.x
  1. Create a PR against branch 0.x, I would have named this PR:

"Backport PR #168 on branch 0.x (Align repo with the extension template)"

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.