search

LSSTDESC / ComputingInfrastructure

Gathering place for CI - Computing and Infrastructure - issues
3 stars 1 forks source link

Using GitHub #16

Closed drphilmarshall closed 3 years ago

drphilmarshall commented 8 years ago

I started a page tracking DESC's use of GitHub, and problems arising from it. Feel free to add to it! We can use this to provide feedback to GitHub at some point: they are keen to support groups like us, and employ someone whose job it is to try and make GitHub work well for scientists. At some point we can draw his attention to this page, and the accompanying discussion on this thread. In the meantime, am I missing anything so far?

drphilmarshall commented 8 years ago

Issue FAO the communications team: @cwwalter @richardxdubois @dkirkby @wmwv @tony-johnson @rachelbean

dkirkby commented 8 years ago

On the topic of jupyter notebooks in github, the current situation is far from ideal because visually small changes to the notebook can result in large, undecipherable git diffs. A good practice is to always restart your kernel and re-run all cells before each commit, which helps minimize diffs. It would be great if the jupyter and github teams could collaborate on improving this workflow!

cwwalter commented 8 years ago

Yes, I agree. After they made rendering available I wrote them (and Arfon I think) and asked them to consider implementing visual diffs to the rendered output.

heather999 commented 3 years ago

Closing. See : https://docs.github.com/en/repositories/working-with-files/using-files/working-with-non-code-files#working-with-jupyter-notebook-files-on-github