************************************************************
***** NOTE: THIS BUG TRACKER IS FOR GERRIT CODE REVIEW *****
***** DO NOT SUBMIT BUGS FOR CHROME, ANDROID, INTERNAL *****
***** ISSUES WITH YOUR COMPANY'S GERRIT SETUP, ETC. *****
***** THOSE ISSUE BELONG IN DIFFERENT ISSUE TRACKERS! *****
************************************************************
Affected Version:
What steps will reproduce the problem?
1. gerrit stream-events
2. Do a trivial rebase with the rebase button
3. Watch for the patchset-added event
Expected: Knowing that the patchset is a trivial rebase
Actual: It looks like any other patchset.
Please provide any additional information below.
This would be nice for scripting purposes - indicating that something is just a trivial rebase, indicating that the patchset came from a cherry-pick, that it's just a commit message update, etc. etc.
My best thought right now is adding a "source" field to the Change objects, then putting that in the JSON output.
I looked at the code briefly yesterday, but it looks like it will take some doing. So I'm going to file this and see if anyone else beats me to it.