You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Shall we try to reduce the CI time for documentation-only changes? I think of running just the docs CI when having the label documentation attached to the issue, and ignoring the whole pytest suite.
That would mean that we need to split our current pytest approach, where we test "normal" tests and documentation tests simultaneously.
This would greatly reduce the time to passing tests in minor (or large) documentation changes, and we would not be held up by increased memory usage, suddenly incompatible dependencies etc. like we were in the last few days.
Yes that would be fine - changes to the docs only should not require pytest to be run. And maybe it would encourage people to work more on the docs as well.
Shall we try to reduce the CI time for documentation-only changes? I think of running just the docs CI when having the label
documentation
attached to the issue, and ignoring the whole pytest suite.That would mean that we need to split our current pytest approach, where we test "normal" tests and documentation tests simultaneously.
This would greatly reduce the time to passing tests in minor (or large) documentation changes, and we would not be held up by increased memory usage, suddenly incompatible dependencies etc. like we were in the last few days.
(I'm thinking in particular of PRs like #2220)
The text was updated successfully, but these errors were encountered: