This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author aeros
Recipients Mariatta, aeros, brett.cannon, docs@python, epicfaace, willingc
Date 2020-03-15.23:35:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1584315331.78.0.923522432024.issue37860@roundup.psfhosted.org>
In-reply-to
Content
> only build PRs that have been tagged "documentation"

My preference would be to have a "preview-with-netlify" label that could be manually added to use the netlify preview on a case-by-case basis. There are a substantial number of trivial PRs (such as typo fixes and similar minor changes) that are automatically labelled as "documentation" which wouldn't particularly benefit from the netlify preview and would needlessly occupy part of the limit.

Personally, I feel that it most largely benefits more significant documentation changes that involve modification of existing markup or the addition of new markup, rather than all documentation PRs. So a manually added label to trigger it makes the most sense to me. This would be very similar to the recently added "test-with-buildbots" label.
History
Date User Action Args
2020-03-15 23:35:31aerossetrecipients: + aeros, brett.cannon, docs@python, willingc, Mariatta, epicfaace
2020-03-15 23:35:31aerossetmessageid: <1584315331.78.0.923522432024.issue37860@roundup.psfhosted.org>
2020-03-15 23:35:31aeroslinkissue37860 messages
2020-03-15 23:35:31aeroscreate