Changelog checkin test: succeed for release PRs #658
@@ Coverage Diff @@ ## master #658 +/- ## ======================================= Coverage 98.97% 98.97% ======================================= Files 136 136 Lines 4697 4697 ======================================= Hits 4649 4649 Misses 48 48
@kmax12 good point, that is true! I guess that's not ideal. The first PR to merge after a release PR goes in will likely be one which was queued up beforehand, meaning the check would have been red. But why make our process more error-prone.
Your saying that made me realize: a more foolproof alternative would be to check the