
Security News
NVD Concedes Inability to Keep Pace with Surging CVE Disclosures in 2025
Security experts warn that recent classification changes obscure the true scope of the NVD backlog as CVE volume hits all-time highs.
balm-git-flow
Advanced tools
The best practices for front-end git flow
npm install -g balm-git-flow
⚠️ NOTE: For Windows users, use
npm install -g balm-git-flow@legacy
First, create a balm.env.js
file in your project root directory (use balm-git doctor
)
Variable Name | Type | Default | Description |
---|---|---|---|
BALM_GIT_FLOW_MAIN | string | 'main' | main branch (source code) |
BALM_GIT_FLOW_RELEASE | string , array | 'release' | production release branch(es) |
BALM_GIT_FLOW_RELEASES | array | ['release'] | all release branches |
BALM_GIT_FLOW_SCRIPTS | array | ['build'] | all build scripts corresponding to the release branches ( the keys of scripts in package.json ) |
BALM_GIT_FLOW_RELEASE_SCRIPTS | string | JSON.stringify({}) | associated scripts and release branches ({ [script: string]: [releases: string[]] } ) |
BALM_GIT_FLOW_BUILD_DIR | string | 'dist' | build out dir (by npm-run-script ) |
BALM_GIT_FLOW_IGNORE_UNCOMMITTED | boolean | false | ignore uncommitted for workflow |
BALM_GIT_FLOW_USE_CUSTOM_MESSAGE | boolean | false | use custom log message |
BALM_GIT_FLOW_REPOSITORIES | array | independent repositories | |
BALM_GIT_FLOW_SITE | string | production release branch for independent repositories |
release scripts settings
Method 1:
BALM_GIT_FLOW_RELEASES = ['test', 'release'];
BALM_GIT_FLOW_SCRIPTS = ['build:test', 'build:release'];
Method 2:
BALM_GIT_FLOW_RELEASE_SCRIPTS = JSON.stringify({
'build:test': ['test-a', 'test-b'],
'build:release': ['release']
});
balm-git doctor
: check the project environmentbalm-git dev <new-branch> [<start-point>]
: create new branch for development from origin main branchbalm-git prod
: release process⚠️ NOTE: For Windows users, use
balm-git-doctor
,balm-git-dev
andbalm-git-prod
FAQs
The best practices for front-end git flow
The npm package balm-git-flow receives a total of 62 weekly downloads. As such, balm-git-flow popularity was classified as not popular.
We found that balm-git-flow 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.
Security News
Security experts warn that recent classification changes obscure the true scope of the NVD backlog as CVE volume hits all-time highs.
Security Fundamentals
Attackers use obfuscation to hide malware in open source packages. Learn how to spot these techniques across npm, PyPI, Maven, and more.
Security News
Join Socket for exclusive networking events, rooftop gatherings, and one-on-one meetings during BSidesSF and RSA 2025 in San Francisco.