Quick tool to check if we are inside a CI environment

Find a file

Jonatan Nilsson a79e6cca09 All checks were successful / deploy (push) Successful in 26s Details readme: Add more information on where they can report missing CI		2024-11-22 06:12:55 +00:00
.forgejo/workflows	forgejo: Fix ci testing	2024-11-22 05:10:06 +00:00
.gitignore	Initial commit	2024-11-18 23:24:04 +00:00
.npmrc	remove package-lock.json	2024-11-19 00:03:24 +00:00
build.sh	Minimize it further and clean it up	2024-11-22 05:08:16 +00:00
in.js	Change from function to boolean return to be compatible with is-ci	2024-11-22 05:58:44 +00:00
LICENSE	Initial commit	2024-11-18 23:24:04 +00:00
not.js	Change from function to boolean return to be compatible with is-ci	2024-11-22 05:58:44 +00:00
package.json	readme: Add more information on where they can report missing CI	2024-11-22 06:12:55 +00:00
README.md	readme: Add more information on where they can report missing CI	2024-11-22 06:12:55 +00:00
test.mjs	Change from function to boolean return to be compatible with is-ci	2024-11-22 05:58:44 +00:00

inside-ci

Returns true if code is running inside CI, otherwise false.

This also works as a drop-in replacement for anyone currently using is-ci.

If your CI is not being detected, feel free to add an issue for it or hit me up on X (formerly Twitter) or on discord as thething_89.

API

const inside = require('inside-ci')

Returns error code 0 if inside CI.

in-ci && echo 'running inside CI'

Inverse of the above:

not-ci && husky install