Johannes Schindelin 3349520e1a coverity: detect and report when the token or project is incorrect ... When trying to obtain the MD5 of the Coverity Scan Tool (in order to decide whether a cached version can be used or a new version has to be downloaded), it is possible to get a 401 (Authorization required) due to either an incorrect token, or even more likely due to an incorrect Coverity project name. Seeing an authorization failure that is caused by an incorrect project name was somewhat surprising to me when developing the Coverity workflow, as I found such a failure suggestive of an incorrect token instead. So let's provide a helpful error message about that specifically when encountering authentication issues. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>		2023-10-05 11:45:46 -07:00
..
workflows	coverity: detect and report when the token or project is incorrect	2023-10-05 11:45:46 -07:00
CONTRIBUTING.md
PULL_REQUEST_TEMPLATE.md