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 steve.dower
Recipients Big Stone, erlendaasland, ned.deily, paul.moore, ronaldoussoren, steve.dower, tim.golden, zach.ware
Date 2020-02-29.11:17:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1582975059.43.0.685806911068.issue38380@roundup.psfhosted.org>
In-reply-to
Content
> (BTW, is it kosher to force push to PRs like this?)

We always squash merge, so you don't need to do it to hide your history. Personally, I do it occasionally when the history is very long and nobody has started reviewing.

Force pushing will reset any reviews, so you'll be forcing reviewers to start again instead of just looking at your updates. Some reviewers (e.g. me) will often defer a full rereview if we don't have a lot of time and someone just force pushed. So in general, avoid it.
History
Date User Action Args
2020-02-29 11:17:39steve.dowersetrecipients: + steve.dower, paul.moore, ronaldoussoren, tim.golden, ned.deily, zach.ware, Big Stone, erlendaasland
2020-02-29 11:17:39steve.dowersetmessageid: <1582975059.43.0.685806911068.issue38380@roundup.psfhosted.org>
2020-02-29 11:17:39steve.dowerlinkissue38380 messages
2020-02-29 11:17:39steve.dowercreate