I’m looking at the errors and it seems pretty clear about what you could do about it:
[ERROR] Paths contain characters outside of ^[a-zA-Z0-9.\-/]*$
This one may be a little tricky, there is a redirection at the last URL, that’s why the 301
The HTTP response status code 301 Moved Permanently is used for permanent URL redirection, meaning current links or records using the URL that the response is received for should be updated. The new URL should be provided in the Location field included with the response. The 301 redirect is considered a best practice for upgrading users from HTTP to HTTPS.
RFC 2616 states that:
[OK] HTTP 200 in OTHERS.lst, url: 'https://raw.githubusercontent.com/anujdutt9/Hackerrank/master/Python3%20Code/Birthday-Cake-Candles.py'
[ERROR] HTTP 301 in OTHERS.lst, url: 'https://raw.githack.com/wjmandella/Birthday-Cake-Candles/master/src/BirthdayCakeCandlesApp.java'
[INFO] Executing function: job_check_commit_message
⧗ input: sol(code): #0 hackerrank, birthdaycakecandles (easy)
- others: 0 in, 5 out, 5 total.
- score: 65 initial, 67 final, 2 progress.
- global-rank: 296196 initial, 226104 final, 700.92 progress.
- national-rank: 234008 initial, 226260 final, 7748 progress.
- effort: 4 hours during challenges, productivity 0.5 points/hour.
✖ header must not be longer than 50 characters, current length is 52 [header-max-length]
✖ found 1 problems, 0 warnings
if pylint and ESLint passes locally but not at the CI, it’s because you may have the wrong configurations
we use pylint for python3, and ESLint with the eslint-config-strict plugin.
moreover, as the error messages say:
We have found some problems with your commit
You can replicate this output locally with:
training $ ./build.sh check_commit_message
more documentation about running ./build.sh as a way to replicate environments:
that’s the only way we support for talents to run the checks locally