Change Details

99% of the time when I am using the `--xprofile` flag, I do the following: # Run `some_command.PHP --xprofile=profile.json`. # Upload the profile to Phabricator with `arc upload profile.json`. # Get the PHID of the newly uploaded file with `echo '{"names": ["F123"]}' | arc call-conduit`. # Open a browser and load `https://phabricstor.mydomain.com/xhprof/profile/$PHID/`. This is very tedious and hard to explain to other... Instead I propose that the `--xprofile` flag automatically uploads the profile to Phabricator and provides an XHProf link to the profilem

99% of the time when I am using the `--xprofile` flag, I do the following: # Run `some_command.PHP --xprofile=profile.json`. # Upload the profile to Phabricator with `arc upload profile.json`. # Get the PHID of the newly uploaded file with `echo '{"names": ["F123"]}' | arc call-conduit`. # Open a browser and load `https://phabricstor.mydomain.com/xhprof/profile/$PHID/`. This is very tedious and hard to explain to other... Instead I propose that the `--xprofile` flag automatically uploads the profile to Phabricator and provides an XHProf link to the profilem

99% of the time when I am using the `--xprofile` flag, I do the following: # Run `some_command.PHP --xprofile=profile.json`. # Upload the profile to Phabricator with `arc upload profile.json`. # Get the PHID of the newly uploaded file with `echo '{"names": ["F123"]}' | arc call-conduit`. # Open a browser and load `https://phabricstor.mydomain.com/xhprof/profile/$PHID/`. This is very tedious and hard to explain to other... Instead I propose that the `--xprofile` flag automatically uploads the profile to Phabricator and provides an XHProf link to the profilem