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.
6 total, 0 approved, 0 rolled up, 0 failed / /
|Sort key||#||Status||Mergeable||Title||Head ref||Assignee||Approved by||Priority|
|1||467||yes||Add a onepass dfa matcher.||ethanpailes:onepass-dfa||0|
|2||472||Add random testing of crates.io regex||ethanpailes:test-crates-io||0|
|3||477||yes||Add nominal no_std + alloc support to regex-syntax||ZackPierce:regex_syntax_no_std_support||0|
|4||483||yes||add benchmark for hyperscan||flier:vs_hyperscan||0|
|5||537||yes||[RFC] regex-capi: expose regex::escape||marmeladema:capi/escape||0|
|6||542||yes||Fix typo in docs||sourcefrog:patch-1||0|