[Total Automation] Validate each meeting's PR

[jmuchovej]

Just a note, when referring to groups... groups := {intelligence, core, data-science, supplementary}

Feature Request, for groups

Description Since Coordinators must submit notebooks as PRs (and given tight integration between the website and groups), we need to automatically verify their changes. NOTE: This shouldn't approve the merge until someone actually takes a look at the content in the notebook.

Needs

• Check that Coordinators were working in <YYYY-MM-DD-slug>.solution.ipynb. IFF:
  • compile the "non-solution" notebook (if this fails, halt PR with helpful feedback)
  • compile the webpage rendition (if this fails, halt PR with helpful feedback)
  • generate the most up-to-date banner.jpg (if this fails, halt PR with helpful feedback)
    • (🍜 Nice to Have) Notify @social-squad in Discord about a failure to generate the banner.
  • attempt to push to Kaggle (if this fails, halt PR with helpful feedback)
    • (🍜 Nice to Have) Notify @director-<group> in Discord about a failure to publish on Kaggle

[Haugf]

Hey John can you explain what a "non-solution" notebook is for me

[jmuchovej]

https://ucfai.org/docs/admin/making-meetings

That should be fairly comprehensive, I think – but, an easy example of this is in #29's description. Currently, this strictly refers to the code blocks of a Jupyter notebook.

#29's description permalink