@codechecks/commit-deployment
Advanced tools
Ship every code change that you make
npm add --save-dev @codechecks/commit-deployment
or
yarn add --dev @codechecks/commit-deployment
Add to your codechecks.yml file:
checks:
- name: commit-deployment
options:
buildPath: "./dist"
# ...
With each pull request you will get a link do current deployment of your frontend app.
interface Options {
buildPath: string;
rootFile?: string;
}
string
Relative (to current codechecks file) path to build that is supposed to be deployed.
optional string
Default: index.html
File considered as root in your build. Attached link will point directly to it.
All contributions are welcomed. Read more in CONTRIBUTING.md
MIT @ codechecks.io
FAQs
Ship every code change that you make
We found that @codechecks/commit-deployment demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer 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
A supply chain attack on Axios introduced a malicious dependency, plain-crypto-js@4.2.1, published minutes earlier and absent from the project’s GitHub releases.
Research
Malicious versions of the Telnyx Python SDK on PyPI delivered credential-stealing malware via a multi-stage supply chain attack.
Security News
TeamPCP is partnering with ransomware group Vect to turn open source supply chain attacks on tools like Trivy and LiteLLM into large-scale ransomware operations.