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.
10 total, 0 approved, 0 rolled up, 0 failed / /
|Sort key||#||Status||Mergeable||Title||Head ref||Assignee||Approved by||Priority||Rollup|
|1||796||yes||Add String::from() snippet||Filius-Patris:master||0|
|2||802||yes||Add tasks.json Support||jcdickinson:master||0|
|3||838||yes||Bump lodash from 4.17.15 to 4.17.20 in /rust-analyzer/editors/code||rust-lang:dependabot/npm_and_yarn/rust-analyzer/editors/code/lodash-4.17.20||0|
|4||840||yes||WIP: Merge both existing and rust-analyzer extension codebase||Xanewok:merger||0|
|5||849||yes||Bump node-fetch from 2.6.0 to 2.6.1 in /rust-analyzer/editors/code||rust-lang:dependabot/npm_and_yarn/rust-analyzer/editors/code/node-fetch-2.6.1||0|
|6||875||yes||Remove angular brackets from `autoClosingPairs`||ibraheemdev:patch-1||0|
|8||587||no||Added Client Side Type Hints||p-avital:master||0|
|9||666||no||[WIP] Add command for creating a new Cargo project||GabrielMajeri:cargo-new-project||0|
|10||683||no||switch exec -> execFile; ShellExecution -> ProcessExecution||AndriesK:master||0|
Open retry log