When listing commits on a repository or posting a change based on a
commit, any HostingServiceError
s that came up would fail to be caught,
resulting in HTTP 500 errors. Furthermore, SCMError
s when posting a
commit for review would lack any detailed error information. It wasn't
entirely clear what the responsibilities of the callers were in some of
these cases either, since it's been a long time since some of these
methods had received any new documentation.
Now, the API endpoints are careful to catch both HostingServiceError
and SCMError
exceptions, and to use their messages for the message
sent back to the caller.
Documentation for all methods in-between have been updated to specify
that these exceptions (and some others) may occur, making it a lot more
clear what the caller is responsible for catching.