Page MenuHomePhabricator

In the "Version Information" panel, try to include branchpoints
ClosedPublic

Authored by epriestley on Dec 23 2016, 4:34 PM.
Tags
None
Referenced Files
F15467394: D17103.diff
Thu, Apr 3, 2:26 PM
F15433785: D17103.diff
Tue, Mar 25, 12:37 AM
F15401737: D17103.id41140.diff
Mon, Mar 17, 7:03 PM
F15398911: D17103.diff
Mon, Mar 17, 1:53 AM
Unknown Object (File)
Feb 20 2025, 11:08 PM
Unknown Object (File)
Feb 18 2025, 12:15 PM
Unknown Object (File)
Feb 9 2025, 3:03 AM
Unknown Object (File)
Feb 9 2025, 3:03 AM
Subscribers
None

Details

Summary

Fixes T12040. In T12039, a user running local patches followed the report instructions as far as grabbing version information, but didn't update or revert their local changes or try against a clean install before reporting.

This obviously isn't ideal for us, but it's understandable (grabbing version information is much easier than upgrading/reverting), and we can do better about making this information useful: when compiling version information, try to figure out the branchpoint from a known upstream master branch by listing remotes, then running git merge-base against them.

Additionally, explicitly document that we want upstream hashes. We have to have a fallback case in this document anyway (for when you can't get to Config) so hopefully this makes it more likely that we get useful information in initial reports.

Test Plan

Screen Shot 2016-12-23 at 8.24.44 AM.png (765×1 px, 218 KB)

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable