-
Notifications
You must be signed in to change notification settings - Fork 429
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
First Blog #2813
First Blog #2813
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #2813 +/- ##
==========================================
+ Coverage 81.45% 81.48% +0.02%
==========================================
Files 144 144
Lines 20054 20054
Branches 3192 3192
==========================================
+ Hits 16335 16340 +5
+ Misses 2909 2906 -3
+ Partials 810 808 -2 |
@skoudoro. I'm actually having trouble writing up a rst file. Since DIPY is very correlated to FURY, i figured that the structure of the rst file would be similar, but it turns out it's not. |
Hi @shilpiprd, Thank you for this first blog post! I will do my first review after @lb-97 and @RafaelNH. |
it is correlated and same syntax. it is just missing an extension ( |
Yeah I actually figured that out, but I wasn't sure if it was ok for me to change an already existing file. |
You can add a check if python >= 3.10 import one version otherwise, the other |
Hey Serge, I think this PR's commit history doens't look like it should, so should i create a new PR which contains all the required changes ? It would look cleaner that way. |
Hi @shilpiprd, Use this PR as a training one. You can squash the commit to reduce the number of commit and improve commit history. Do NOT create a new PR. I assure you that all you future PR will be easier to manage after learning this. EDIT: this means (rebase and squash) |
612c7f2
to
29221e2
Compare
I think I squahsed all the needed commits together, "2nd_Final_commit " should be good. |
@shilpiprd, I think you can squash all commits to a single commit, that should suffice. |
Are you sure ? Because the structure of the rst file has been removed in 2nd commit, but it's there in the final squashed commit. If I squash them then wouldn't 2nd commit overwrite all changes (i.e remove the top structural part )? Same for 1st commit, I've changed some lines in the rst blog post. |
If you squash them using |
yeah, I think it's done now. Thanks @lb-97 ! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @shilpiprd,
See below my review. After that, it should be ready to go.
@lb-97, can you look at my review also to get inspired for the future one.
Thanks to both of you
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
be careful, you committed doc/posts/2023/2023_05_29_Shilpi_week1.pdf accidentally.
to remove
yeah it's supposed to be an rst file right? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @shilpiprd,
See below my review. Also, link does not work. Please check how to do a link in rst.
Thanks
I hope with this all the links would work, please let me know if any other changes are required. |
Thanks @shilpiprd , merging |
This folder should provide a place to put all the blog posts.