- User Since
- Oct 2 2014, 8:30 PM (322 w, 1 d)
Apr 18 2017
Aug 5 2015
I've run into this problem by copy pasting my commit message into the description field so that I can update the description when my commit updates. If I also copy in the metadata fields, this breaks the parser, e.g.
Oct 16 2014
Most search & find interfaces give a visual cue when they wrap around, however. Would a patch along those lines be accepted?
Could we solve the problem of knowing what file a patch is for without scrolling just by adding a tooltip to, say, the line numbers? (Even the browser tooltip would work.) It doesn't have to be immediately visible, I just want to find out the file without scrolling!
Oct 6 2014
Thank you for the pointer on history mutability!
I'd also like to chime in that it is frustrating to (1) make sure all of patches in the series have correct dependency information (T6232), and (2) that the Phabricator web interface doesn't have any affordances for handling patch series like this (e.g. collecting all the patches in a logical series into a single summary page.)
Oct 2 2014
Sorry for all the noise, but is this WONTFIX for having Arcanist warn when the diff is really big?
To clarify, the severity determines whether or not the error is reported always, or only if it was touched by the commit.