Would enforcing a warning-free document in sphinx be merged? We could check that during the travis build. I noticed multiple times syntax errors (warnings*) getting merged time to time into master. It would give that:
@/all hey everyone, it’s becoming harder and harder to follow the chat here as questions are often pushed off-screen before anyone has a chance to reply, we’re considering moving to Spectrum (https://spectrum.chat) as they’ve just announced merging with GitHub; what are your thoughts?
@NyanKiyoshi sorry, only just saw your question about doc strictness (hence why we want to move away from Gitter), I would very much like a checker for that but I think Code Climate would be a better place and could help other projects as well
@patrys@Pacu2 Oh so are you in a sense saying I can make more file changes as it's running and it'll update per say, not sure if you can understand what I'm trying to say there. And in other funny news, y'all are saying that I've wasted the last 3hours of my life. 😭😂
@patrys could be really manage to get a full check over the RST files? I was thinking about building the sphinx docs during the travis build. I'm really not sure about doing full checks over codeclimate, as I was thinking about checking if the build passes or not (with a strict syntax). Otherwise... Maybe we could manage to trigger automatically a build on GitHub PR whenever a change is detected in docs/. That could be possible (I guess).