snowex-hackweek / website-2022 Goto Github PK

Found a typo - in the section 'Setting up Git' and below the pink text 'jupyterlab-git' -- the second occurrence of pink text has 'jupyterlag-git'. That is, 'lag' instead of 'lab'.

see #96 (comment)

It's not uncommon for rendered HTML versions of notebooks to be large, but it would be great for CI to flag especially large outputs. cc @jomey @ZachKeskinen

This warning is currently buried under the push the commit or tag dropdown in the log https://github.com/snowex-hackweek/website2022/runs/7221242444?check_suite_focus=true

remote: warning: File tutorials/uavsar/2_types_of_uavsar_images.html is 82.99 MB; this is larger than GitHub's recommended maximum file size of 50.00 MB        
[1316](https://github.com/snowex-hackweek/website2022/runs/7221242444?check_suite_focus=true#step:4:1323)
  remote: warning: GH001: Large files detected. You may want to try Git Large File Storage - https://git-lfs.github.com./

I've noticed lots of tutorials each starting with a slightly different piece of code to check if there is a a valid .netrc, and if not, create one. This has led to errors in past hackweeks, where for example special characters aren't recognised, untested code creates (or overwrites) malformed ~/.netrcs, etc.

@egreckase (+ @betolink) would you recommend sticking with the earthdata library across tutorials for this critical step? Or adding a script that everyone can run on the jupyterhub (https://nasa-openscapes.github.io/2021-Cloud-Hackathon/tutorials/04_NASA_Earthdata_Authentication.html)?

Our current recommendation is here and could be revised https://snowex.hackweek.io/preliminary/earthdata.html#configure-programmatic-access-to-nasa-servers

Thus they are appearing like {{github_org_url}} in this page for example:

https://icesat-2.hackweek.io/preliminary/git.html

and others.

Well, I reviewed approved @meganmason 's pull request for her bio and that went great! Then I moved on to @ZachKeskinen 's pull request for his bio, which didn't have Megan's bio. I tried to resolve merge conflicts, by copy/paste to make one team file that had both Megan and Zach, trying to be very careful with indentation. I failed to preview the result, and committed the merge. It failed the "buildresources" test. Somehow it doesn't seem like it broke the website, which is looking like it did before this merge? @scottyhq ?

Found a typo - in the section 'Setting up Git' and below the pink text 'jupyterlab-git' -- the second occurrence of pink text has 'jupyterlag-git'. That is, 'lag' instead of 'lab'.

We should tag a release and link to Zenodo as we did for the 2021 event !