Right now we don't have any way to meaningfully order commits from MySQL. We should use the git log order to place an order column in the versioncontrol_operation_labels table to say what order a commit was in a given branch.

CommentFileSizeAuthor
#1 0001-Issue-1089852-Add-a-weigth-field-to-versioncontrol-o.patch2.11 KBmarvil07

Comments

marvil07’s picture

marvil07 commented
Title: add order to versioncontrol operations labels so we can order commits » Add a weigth field to {versioncontrol operations} tables so we can order commits
Project: Version Control API -- Git backend » Version Control API
Component: Code » API module
Assigned: Unassigned » marvil07
Category: task » feature
Status: Active » Needs review
Issue tags: +git phase 3
StatusFileSize
new 0001-Issue-1089852-Add-a-weigth-field-to-versioncontrol-o.patch2.11 KB
marvil07’s picture

marvil07 commented

The related versioncontrol git issue: #1089910: Fill weight for versioncontrol_operations

sdboyer’s picture

sdboyer commented
Title: Add a weigth field to {versioncontrol operations} tables so we can order commits » Add a weight field to {versioncontrol operations} tables so we can order commits

Title was drivin me nuts :P

marvil07’s picture

marvil07 commented
Assigned: marvil07 » tizzo

@tizzo: It would be great to receive your review here.

sdboyer’s picture

sdboyer commented
Status: Needs review » Postponed
Issue tags: +vc-next

this is part of the whole repo families discussion, at least in some way. and i'm still not convinced about weighting being something that's efficient for us to maintain in an rdbms.

marking vc-next, and postponed.