Open GoogleCodeExporter opened 9 years ago
That sounds a bit complicated. IMO it's easier for both parties if the issue
tracker
pings Rietveld and does changes when the issue state changes. FWIW, here's how
git-cl
does this: http://neugierig.org/software/git/?url=git-cl/tree/git-cl#n340
Original comment by albrecht.andi
on 19 Mar 2010 at 10:37
Does rietveld have any documented API for such web integration?
Original comment by techtonik@gmail.com
on 19 Mar 2010 at 11:30
Not yet, but I'm currently writing up a documentation on how to talk
programmatically
to Rietveld. For now the following URLs might be of interest: /ISSUE/close,
/ISSUE/description, /api/ISSUE, where ISSUE is the review issue number. The
JSON object
returned by /api/ISSUE might slightly change sometime soon.
Original comment by albrecht.andi
on 19 Mar 2010 at 11:36
Are you sure there won't be other enumerable objects in rietveld to bind
/api/NUMBER/
solely for issues? I would bind /api/NUMBER/ for different version of API
moving issues
into /api/issue/NUMBER namespace.
Original comment by techtonik@gmail.com
on 19 Mar 2010 at 11:56
Original comment by techtonik@gmail.com
on 28 Sep 2010 at 10:16
Original comment by albrecht.andi
on 6 Apr 2012 at 7:45
Original issue reported on code.google.com by
techtonik@gmail.com
on 19 Mar 2010 at 6:57