Manuel Kaufmann

@agjohnson checking for `is_debug` property from each `BuildCommand` makes sense. I think it will be easy to add something similar to [`record=False`](https://github.com/readthedocs/readthedocs.org/blob/d13c934c3acbffd6148ed125c4dd9c511f9e9108/readthedocs/doc_builder/backends/sphinx.py#L308) for those commands that we don't want to...

The plan that we have sounds good to me!

I think that I don't fully understand your proposal. So, nothing that I'm about to write may make sense 😄 At simple sight, it sounds pretty complex to me. It...

@agjohnson > Right now, there is a build button on the project dashboard pages, and users can click that to start/restart a build. This effectively calls "trigger_build(project_pk)". I'm describing a...

I would avoid showing "fantasy commands" because it will generate more confusion than other things. They are going to be harder to explain to users. If we want to show...

> But either way, we're already hacking in the output of multiple files using `cat`, and haven't had much (any?) negative feedback here. Plus this is debug information, so I'm...

I prefer to avoid fantasy commands if possible. I'd prefer to use the new build notifications to show warnings / tips or similar for those checks we want to do...

> I would like to get this particular issue in so we can show/hide debug commands more consistently. It seems like we still want this, correct? Yes. This is the...

Yes, `cat` is not a replacement for the better UX we are talking about here. It's just the minimal and easier way to implement a step that gives us an...

Yeah, I'm fine with better notifications. Maybe we want to make that part of the work on #9279 and #3399 We need to probably set two different thresholds here: 1....