Closed GoogleCodeExporter closed 9 years ago
Also need the full commit message, and other details.
Original comment by sza...@google.com
on 13 Dec 2013 at 7:52
If you're trying to prioritize API enhancements, this one is needed for
Chrome's commit monitoring/alerting/bug-updating tool, which uses the gitiles
API to avoid needing local git checkouts.
Original comment by mmoss@google.com
on 26 Feb 2014 at 9:22
mmoss: Am I correct in understanding that the /+log/commit?format=JSON&n=1
workaround doesn't work for you (i.e. you need changed files or something else
not in that output)?
Original comment by dborowitz@google.com
on 26 Feb 2014 at 9:55
I'm using the +log API already, and that's working well, but it doesn't give me
everything I need for the commits, in particular the file listing mentioned in
the original bug comment.
Original comment by mmoss@chromium.org
on 26 Feb 2014 at 10:08
Thanks for clarifying. That also makes the tense in your previous comment make
more sense, since you are indeed already using it.
Original comment by dborowitz@google.com
on 26 Feb 2014 at 10:14
Slightly off-topic, but there was discussion previously about serving up raw
blob contents by forwarding to a different domain (to avoid XSS vulnerability).
Any movement on that?
Raw blobs and detailed commit stats in JSON are killer features for us.
Original comment by szager@chromium.org
on 26 Feb 2014 at 10:21
szager@: https://code.google.com/p/gitiles/issues/detail?id=7
Original comment by mmoss@chromium.org
on 26 Feb 2014 at 10:23
https://gerrit-review.googlesource.com/55207
Original comment by dborowitz@google.com
on 19 Mar 2014 at 10:07
Original issue reported on code.google.com by
dborowitz@google.com
on 13 Dec 2013 at 7:45