gitiles feature discovery

[spearce]

Originally reported on Google Code with ID 47

It would be great if there was a doc that listed how gitiles URLs worked.
E.g.
- ?format=TEXT for base64-encoded file download
- ?n= and ?s= for log number/start offset
- the ultimate resolution to issue 26 (filter by author, others)
- other awesome gitiles features I don't even know about because they're not documented
:)

Reported by None on 2014-04-25 10:29:54

[spearce]

It would be great if there was a doc that listed how gitiles URLs worked.
E.g.
- ?format=TEXT for base64-encoded file download
- ?n= and ?s= for log number/start offset
- the ultimate resolution to issue 26 (filter by author, others)
- other awesome gitiles features I don't even know about because they're not documented
:)

Reported by None on 2014-04-25 10:29:54

[spearce]

I agree, we totally need documentation of the URL structure and JSON formats. 

I remember reading not too long ago about a kind-of-standard way of describing URL
formats using placeholders that you present in a JSON endpoint but I can't for the
life of me remember what it's called.

Reported by None on 2014-04-27 12:43:12

[spearce]

Issue 54 has been merged into this issue.

Reported by None on 2014-07-09 15:02:36

[spearce]

Chromium has a "Gitiles Tricks" page with APIs that people find useful / ask about a
lot: http://www.chromium.org/developers/change-logs

Reported by None on 2014-09-08 16:26:33

[kjellander-unity]

I wrote this doc mostly to share with my team, but I guess it could be converted to a more useful MarkDown page if the examples were a little more generic:
https://docs.google.com/document/d/1Ew1NLoOvmIdCwWbR_3068Mjmp2YC2Ln9BI0ayjZ9KlY/pub
I don't have the time to do so right now, but if someone else wants to do that, feel free to do use its content.