Change Details

>You should make use of proper HTTP status codes in order to inform users. You can use codes like 201 or 202 to acknowledge receipt of payload that won't be processed (for example, a payload delivered by a branch that's not the default). Reserve the 500 error code for catastrophic failures.

>GitHub is explicit in telling you when a resource has moved by providing a redirect status code. You should follow these redirections. Every redirect response sets the Location header with the new URI to go to. If you receive a redirect, it's best to update your code to follow the new URI, in case you're requesting a deprecated path that we might remove. https://developer.github.com/v3/#http-redirects

>You should make use of proper HTTP status codes in order to inform usersGitHub is explicit in telling you when a resource has moved by providing a redirect status code. You should follow these redirections. Every redirect response sets the Location header with the new URI to go to. You can use codes like 201 or 202 to acknowledgeIf you receipt of payload that won't be processed (for exampleve a redirect, a payload delivered by a branch that's notit's best to update your code to follow the default).new URI, Reserve the 500 error code for catastrophic failures.in case you're requesting a deprecated path that we might remove. https://developer.github.com/v3/#http-redirects