This note is about two things: 1. I added a CI pipeline for contributors to test their website & docs changes on the staging site [1]. To speed it up, it only generates the Jekyll and Python API parts of the site. Usage info is in the PR's [2] description. I was going to add a guide for this on Dev Wiki. Which brings be to my second point...
2. There's no info in the dev wiki's development guide [3] on how to deal with the CI issues that inevitably stall every pull request. We can add to this guide so that contributors can have a better experience, know what to actually do, and to make sure that CI issues are being reported and handled. Would someone like to collab on that? I'd need assistance on the git magic for all of the what-if scenarios. [1] https://mxnet-beta.staged.apache.org/ [2] https://github.com/apache/incubator-mxnet/pull/16411 [3] https://cwiki.apache.org/confluence/display/MXNET/Development+Guide Cheers, Aaron
