Cleber Rosa writes:
> When an HTTP GET request fails, it's useful to go beyond the "not
> successful" message, and show the code returned by the server.
>
> Signed-off-by: Cleber Rosa
Reviewed-by: Alex Bennée
> ---
> scripts/ci/gitlab-pipeline-status | 4 +++-
> 1 file changed, 3 insertion
On 2/22/21 4:32 PM, Cleber Rosa wrote:
When an HTTP GET request fails, it's useful to go beyond the "not
successful" message, and show the code returned by the server.
Signed-off-by: Cleber Rosa
---
scripts/ci/gitlab-pipeline-status | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
When an HTTP GET request fails, it's useful to go beyond the "not
successful" message, and show the code returned by the server.
Signed-off-by: Cleber Rosa
---
scripts/ci/gitlab-pipeline-status | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/scripts/ci/gitlab-pipeline-stat
