Some of these need to be rebased. I wonder which ones…
Gerrit should show "Can Merge: Yes / No" status on my dashboard.
When you have thirty patches you really are not going to check every single one to see if they need action.
See Also: T65995: Provide search operator "is:mergeable" in Gerrit
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | • demon | T52297 Show "Can Merge: Yes / No" status on dashboard | |||
| Resolved | • demon | T70271 Upgrade gerrit to 2.12 | |||
| Declined | Bawolff | T106666 Consider changing gerrit default change screen to CHANGE_SCREEN2 | |||
| Resolved | • jcrespo | T139755 Need snapshot of 'reviewdb' on spare machine to test gerrit schema upgrades | |||
| Resolved | • demon | T131903 Update gerrit sshkey in role::ci::slave::labs when upgrade to Jessie happens | |||
| Resolved | Dzahn | T125018 replace gerrit server (ytterbium) with jessie server (lead) | |||
| Resolved | RobH | T123132 Need spare server to upgrade/migrate gerrit | |||
| Resolved | • Cmjohnson | T123531 check for memory upgrade for lead | |||
| Resolved | • demon | T126794 setup/deploy server lead as jessie gerrit server | |||
| Resolved | • Cmjohnson | T141415 decom ytterbium (datacenter) |
I don't like this idea...the dashboard is cluttered enough as it is.
Plus I think it'll encourage needless rebasing. People don't need to rebase every time a patch is a bit behind master...just when they're going to merge and there's conflicts (or if there's something in master you want you work to be based on).
I don't like the idea of putting it on the dashboard either, but could we please have a way to search by Can Merge status?
For search we would need Gerrit 2.9 which has the is:mergeable search stanza. So that is blocked on T70271: Upgrade gerrit to 2.12.