Skip to content

build: lint commit message in separate Travis job

https://github.com/nodejs/node/pull/23739 changed the Travis Linter job so that it never fails if the first commit message linting step fails. This was done in response to a false positive which we speculate was perhaps due to hitting the GitHub API rate limit or a network issue (https://github.com/nodejs/node/pull/23739#issuecomment-436271622).

This PR:

  • Moves the first commit message linting step to a separate Travis job. This will keep the amount of output in the individual jobs down.
  • Runs the script in bash debug mode to capture any issues communicating with the GitHub API (e.g. network issues, rate limits).
Checklist

Merge request reports

Loading