@pmav99 I think the style protection setup for searvey needs to be more lenient!! Every time I go back to fixing a 5min bug in searvey I need to spend hours trying to figure out how to submit the code! I'm using conda environment for my dev, and somehow it doesn't like pipx and precommit and black and everytime something gets messed up.

I can no longer make init in my env (new env I create from scratch on conda). It's just too much!! This is the fix for the bug @AtiehAlipour-NOAA discovered. But I don't know how to move forward with creating a clean PR for merge given the issues I keep having on my env with pipx and precommit.

Update
I am now able to make init, but I still fail in the precommit black and reorder-python-imports. If I manually run black all is fine!!

Yeah, this happens because reorder-python-imports and black have made an incompatible choice WRT to whitespace after module docstrings. Your commit adds an extra line here: https://github.com/oceanmodeling/searvey/pull/139/files#diff-693873d8dcc79e85f6d48197d036272497c1d339ec3c218a87ed678f40489030R12
Reorder-python-imports removes this line and black adds it again. The end result is that the file is identical to the state it was before you run pre-commit (which is why it is not easy to understand what happens) but since both checks changed the file they both fail.

For more info check e.g. asottile/reorder-python-imports#66 and many other issues in the reorder-python-imports bugtracker.

I am happy to discuss and review improvements to our CI :)

Thank you @pmav99 it now makes sense! I think the main thing is having a good feedback! I couldn't get it why it would just gives me error on both of these tools. Let's talk about possible solutions during our next meeting. Failing during commit is very annoying, so maybe we should not do all of the reordering, etc. at the same time during commit. Let's for example do Black only during precommit and do the rest for merge tests, or something like that

OK, I revoked all the changes I had done in this branch because I merged them on master via #140

@SorooshMani-NOAA can you please rebase? There will be a minor conflict which will need to be resolved (the empty line after the module docstring). I could do it myself but resolving the conflict would show me as the COMMIT_AUTHOR instead of you.

After rebase, if CI is happy, feel free to merge.