This will create a new pull request consisting of 0 PRs.
A rollup is useful for shortening the queue, but jumping the queue is unfair to older PRs who have waited too long.
When creating a real rollup, try to be fair to the PRs not rolled up. You may pick one of these strategies:
Always include the first approved PR in the rollup. Then give the new pull request the highest priority (p=100);
After creating the rollup, give it a fairly high priority (p=10), then assign even higher priorties (p=20, ...) to every PRs older than the oldest rolled up PR.
12 total, 1 approved, 0 rolled up, 1 failed / /
|Sort key||#||Status||Mergeable||Title||Head ref||Assignee||Approved by||Priority|
|1||1551||yes||Add support for Azure DevOps badge||robertohuertasm:azure-devops-badge||0|
|3||1561||yes||Record who published crate versions||Andy-Bell:record-who-published-crate||0|
|4||1576||yes||Add a whatsdeployed.io badge to README||notriddle:patch-1||0|
|5||1586||yes||Add the ability to flag a user as deleted in GH||sgrif:sg-deleted-users||0|
|6||1589||yes||Reject publishing of crates that depend on an alternative registry||jtgeibel:deny-alt-registry-deps||0|
|7||1595||yes||Add an extra check to `verify_tarball()`.||icefoxen:verify-no-parent-dir||0|
|8||1596||yes||Rate limit the crate publish endpoint||sgrif:sg-realip||0|
|9||1496||no||Switch to use AWS signature v4||cswindle:aws-signature-v4||0|
|10||1543||no||Allow multiple keywords in crate search||pwoolcoc:allow-multiple-keywords-in-search||0|
|11||1588||no||Move index updates off the web server||sgrif:sg-background-jobs||0|
|12||1501||error||no||Revert to release version of ring||ishitatsuyuki:cargo-toml-cleanup||carols10cents||0|