-
Notifications
You must be signed in to change notification settings - Fork 27
pint-xarray blog post #251
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@andersy005, do I need to do something special to be able see a log of the failing build? I get 404s when I try to follow the links. |
for more information, see https://pre-commit.ci
Co-authored-by: Anderson Banihirwe <[email protected]>
Co-authored-by: Anderson Banihirwe <[email protected]>
Co-authored-by: Anderson Banihirwe <[email protected]>
6756c70
to
e035caa
Compare
Is there anything more that needs to be done here? Do we need to release pint-xarray first? |
The gentlest of bumps on this... is this ready for prime time? Happy to merge this tomorrow if there are no additional changes. |
Not entirely, but since it doesn't promote any antipatterns I think it
should be fine. Thanks a lot, @TomNicholas!
|
Okay let's merge it then! |
In order to start moving again, and also to see how the rendered version would look like, here's the current state of the
pint-xarray
blog post.I am hoping to finalize it (and the
pint-xarray
release) in the next few days / over the week-end so we can ask for feedback in the dev meeting next week and publish it soon after that.cc @TomNicholas