@mixmaxhq/commitlint-jenkins
Advanced tools
Lint all relevant commits for a change or PR on Jenkins CI
A wrapper for commitlint that determines the appropriate commit range in a Jenkins build. Adapted
from @commitlint/travis-cli.
Only supports git projects, assumes a single repository (i.e. does not explicitly support cross-
repo pull requests), and doesn't support renaming the remote to something other than origin. We
welcome pull requests!
--if-ciIf commitlint-jenkins is run outside of a CI context, it will fail. This flag simply ignores the
failure, for use-cases where commitlint-jenkins should be run from a script shared with a non-CI
workflow.
--pr-onlyIf commitlint-jenkins is run in CI in a build that isn't a pull request build, silently exit.
This flag is particularly handy for use with
@mixmaxhq/semantic-commitlint.
GH_TOKEN=xxx npx semantic-release --no-ci
FAQs
Lint all relevant commits for a change or PR on Jenkins CI
We found that @mixmaxhq/commitlint-jenkins demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
Security News
Research
A supply chain attack on Rspack's npm packages injected cryptomining malware, potentially impacting thousands of developers.
Research
Security News
Socket researchers discovered a malware campaign on npm delivering the Skuld infostealer via typosquatted packages, exposing sensitive data.