Skip to content

Conversation

@keflavich
Copy link

Title says most of it.

I need to rebase this, but this is my first PR and is also my first test of the new build system.

cc @hpparvi

@review-notebook-app
Copy link

Check out this pull request on  ReviewNB

See visual diffs & provide feedback on Jupyter Notebooks.


Powered by ReviewNB

@keflavich
Copy link
Author

the pre-commit fixes severely broke my attempts to further edit the file. It is not good that they were included in this case.

@keflavich keflavich force-pushed the refactor_for_specreduce branch from e88973c to 85b87fe Compare June 27, 2025 01:17
@keflavich keflavich force-pushed the refactor_for_specreduce branch from 34b15d8 to a1d242e Compare June 27, 2025 01:19
@keflavich
Copy link
Author

re: my previous comment - it's not great that I can push, have pre-commit change my commit, then be prevented from pushing the next time. pre-commit introduces conflicts that are hard to resolve.

the advice to users is probably: you really need pre-commit to run locally. But in this case, I think that deletes your local rendering, which is itself a pain... I'm not sure the solution, just shouting in the wind

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant