Page MenuHomePhabricator

Ability to view the revision follow-up tree
Open, LowPublic

Description

Author: happy.melon.wiki

Description:
CR groups revisions into 'trees' based on the commit summary: the revision is assumed to be a follow-up to any revisions named in the summary, and follow-up revisions are listed below the diff on the original commit. But users can make typos, forget to mention the previous commit, or otherwise fail to build a proper tree. And in fact you can't really *see* the full tree structure anywhere, only the immediate parent/child relations.

It would be preferable if the full tree structure for at least a couple of levels either side was visible below the diff, and that there was a way to edit the structure, either in-place or via a separate page.


Version: unspecified
Severity: enhancement

Details

Reference
bz26416

Related Objects

StatusSubtypeAssignedTask
OpenNone
ResolvedNone

Event Timeline

bzimport raised the priority of this task from to Low.Nov 21 2014, 11:15 PM
bzimport set Reference to bz26416.
bzimport added a subscriber: Unknown Object (MLST).

The structure is already editable in trunk, see bug 25638. Being able to view the full tree structure (not just first-level follow-ups to a rev, but nth-level follow-ups and predecessors as well) would also be useful, yes.

Do you want a list of what this rev links to in it's summary (predecessors) (and any manually referenced), followups to it's followups in the table (or similar) at the bottom?

(In reply to comment #2)

Do you want a list of what this rev links to in it's summary (predecessors)
(and any manually referenced), followups to it's followups in the table (or
similar) at the bottom?

A more graphical "tree" would be cool, but a predecessor list and an infinite-depth follow-up list would be useful already.

How about an API module first? Maybe someone wants to innovate with the data...

(In reply to comment #4)

How about an API module first? Maybe someone wants to innovate with the data...

I was just thinking the same. It's certainly something that could be done better ajaxy

Just thinking what we need in the API module (or adding to)...

A list of all followup revisions? Maybe with some basic information?

(In reply to comment #6)

Just thinking what we need in the API module (or adding to)...

A list of all followup revisions? Maybe with some basic information?

Done for bug 29916 in r96321, displays same info as we get at the bottom of the CR display pages

Reedy added a project: MediaWiki-API.
Reedy moved this task from Unsorted to Non-core-API stuff on the MediaWiki-API board.
Reedy removed a subscriber: wikibugs-l-list.