1134397 - improve notification of nonFastforward changes in vcs-sync

Status: RESOLVED WONTFIX

(Developer Services :: General, task)

Description

[Hal Wine [:hwine] use NI!]

Definitely an issue for legacy (see bug 1130271 comment 50)

Challenge will be not over reporting, as legacy logs an error on every conversion.

Comment 1

[Hal Wine [:hwine] use NI!]

ni: pmoore - what notification is there of attempted nonFastForward commits on modern? And what processes does that trigger? I'll follow that as closely as possible on the legacy, so we don't create new processes.

Comment 2

[Pete Moore [:pmoore][:pete]]

Attachment: vcs2vcs Successful noop conversion for l10n 157s.pdf

Hey Hal,

An email gets sent, like the one attached. The email subject is a bit misleading, but there is a separate bug about that with a long history (bug 939817).

Pete

Comment 3

[Pete Moore [:pmoore][:pete]]

(In reply to Hal Wine [:hwine] (use needinfo) from comment #0)
> Definitely an issue for legacy (see bug 1130271 comment 50)
> 
> Challenge will be not over reporting, as legacy logs an error on every
> conversion.

Modern vcs sync too, on every failure...

Comment 4

[Pete Moore [:pmoore][:pete]]

Hal, is this a WONTFIX or INVALID now? Is legacy still alive?

Comment 5

[Hal Wine [:hwine] use NI!]

it's alive, but dying soon -- with no interest for this long, it's a WONTFIX