r?foo at beginning of a commit message or subsequent line doesn't (always?) tag the reviewer

NEW
Unassigned

Status

2 years ago
2 years ago

People

(Reporter: jgilbert, Unassigned)

Tracking

Details

(Reporter)

Description

2 years ago
This seems to have happened a couple times now.

Git wraps first commit lines early, and has a 72-char hard limit. This wrapping sometimes leaves the r?foo off the first line, and it doesn't get picked up by hg push review integration.

To get around this, I tried starting commits with r?foo, but this seems to (sometimes?) not work.
(Reporter)

Comment 1

2 years ago
The final commit here did not pick up the start-of-line "r?jrmuizel":
https://bugzilla.mozilla.org/show_bug.cgi?id=1262265
(Reporter)

Comment 2

2 years ago
FWIW, the workaround I'm using now is to include a leading space:
" r?foo - blah blah blah"
You need to log in before you can comment on or make changes to this bug.