I understand that this may not be clear to a beginner, but how to use GitHub and git doesn't depend on what language you program in. The first thing you need to do it learn the basics of using GitHub and git. There are many tutorials other there. If after this you still have questions about a Mathematica-specific workflow, feel free to ask a new question. But please be specific about what problem you encountered.
– SzabolcsApr 09 '21 at 10:43
4
Tip: Since .nb files are not written by hand, they are not a very good fit for git. Plain text .m or .wl files can reap all benefits, but not .nb.
– SzabolcsApr 09 '21 at 10:44
I agree with @Szabolcs and I also vote to close this question as off-topic
– Apr 09 '21 at 11:15
@Szabolcs Since I couldn't find the answer in github tutorials, I tempted to ask my question here!... As you may know, importing .py or .ipynb files are easy in github, but .nb files are tricky. Your suggestion for using .m or .wl is good but it still doesn't work like .py.
– حسین سلحشورApr 09 '21 at 14:01
@حسینسلحشور all plain-text files work fine through Git. If you issue is just that it doesn't display like it does in the regular Mathematica front-end, well that's beyond our control. Only GitHub can change that.
– b3m2a1Apr 09 '21 at 19:35
.nbfiles are not written by hand, they are not a very good fit for git. Plain text.mor.wlfiles can reap all benefits, but not.nb. – Szabolcs Apr 09 '21 at 10:44.pyor.ipynbfiles are easy in github, but.nbfiles are tricky. Your suggestion for using.mor.wlis good but it still doesn't work like.py. – حسین سلحشور Apr 09 '21 at 14:01