Closed darribas closed 5 years ago
Mmm... There seems to be conflicts, not sure why. Any ideas?
Also, before we merge, should we tag for easy access the current version of master
? The change is very significant.
I encountered similar conflicts when pulling from your fork. Not sure why...
I think it makes sense to tag the current version of master.
@darribas For adding spaghetti
into the jupyterbook infrastructure, would I simply add it into the packages.yml
?
@darribas I think I resolved these conflicts. I pushed up to my origin so have a look at the comparison if that was pr'd into your master.
Thanks to @sjsrey, conflicts seem to be resovled, so merging this ahead.
This PR brings all the work to revamp the repository as an automated
jupyter-book
that pulls in notebooks available from federated packages and serves it online. Issues can be tracked with thenbs2.0
tag. The idea is that, from here on, development is centralised on thepysal
organisation account and contributors issue PRs in the same way as they'd do for code.