Open Philanoe opened 2 years ago
This is a good idea. What do you think about these weights for the fix?
Importance: 3 Urgency: 2 Complexity: 3
For tables in markdown, you can use this Markdown Table Generator here: https://www.tablesgenerator.com/markdown_tables
For tables in markdown, you can use this Markdown Table Generator here: https://www.tablesgenerator.com/markdown_tables
Thank you very much. I would have prefered an offline tool but this one functions perfectly. And a great news is that after loading the web pages, it can work offline (table updates tests after disconnecting my wifi) !
This is a good idea. What do you think about these weights for the fix?
About the kernel metadata modification on Jupyter, I do not really know the impact of them. My feeling is that Kaggle, Colab and Jupyter do not really deal with them by default. Any expertise about notebooks metadata in general ? About the weights, could you precise what is the scale of them ? Out of 5 ? Out of 10 ? So far, I do not understand the problem well enough to give good weights so I trust you.
Hi, I found a way to cancel the modification of metadata easily :
We can use git add -p
to check each modification one by one, pressing y for wanted modifications and n to discard unwanted modifications, or use Git-Cola which does the same thing through an interface.
I found this tips here : https://filip-prochazka.com/blog/git-commit-only-parts-of-a-file#:~:text=If%20they%E2%80%99re%20separated%20by%20some%20not%20modified%20lines%2C,lines.%20Luckily%2C%20you%20can%20use%20the%20e%20command%21
I do not know why, but I found that when modifying a notebook from James with Jupyter Lab, git cannot retrieve the details of the modifications. When modifying it with Jupyter notebook, I have not this problem. So, there must be some slightly differences in the way they code the notebooks. So, in the future, I will keep using Jupyter notebook so that my pulling request are more readable (we can see the modified lines).
Hi, this is a documentation problem, as well as a tools sharing problem It can be solved with a branching strategy that will be soon implimented
Hi, I have started modifying some notebooks with Jupyter to perform pulling request in the future, and I would like your advise for some technical questions :