Security News
JSR Working Group Kicks Off with Ambitious Roadmap and Plans for Open Governance
At its inaugural meeting, the JSR Working Group outlined plans for an open governance model and a roadmap to enhance JavaScript package management.
branch-name-commit-modifier
Advanced tools
This module installs a commit-msg hook that will prepend a project issue number inferred from either the commit message or the current branch name. More details in the examples section below.
This module installs a commit-msg hook that will prepend a project issue number inferred from either the commit message or the current branch name. More details in the examples section below.
In your package.json add the field config
and then add a subfield titled branchNameCommitModifier
.
This is where you will put your options.
E.G.
{
"name": "cool-stuff",
"version": "1.0.0",
"description": "this is some cool stuff",
"main": "index.js",
"scripts": {
"test": "rm -rf /"
},
"author": "big dumb idiot face",
"license": "MIT",
"config": {
"branchNameCommitModifier": {
"preChar": "{",
"postChar": "}",
"projectName": "TESTPROJECT"
}
}
}
preChar
: this is the character that will appear before the issue prefix.
postChar
: this is the character that will appear after the issue prefix.
delimiter
: this is the character that will appear between the project name and the issue number.
projectName
: this is the name of the project that will be searched for.
{
preChar: '[',
postChar: ']',
delimiter: '-'
}
The default for projectName
is any sequence of characters A-Z.
The following will match the default projectName
value.
AWESOMEPROJECT
EXPLODINGcapybaras
LearnToChopOnions
The follow will NOT match the default projectName
value.
AWESOME-PROJECT
E-X-P-L-O-D-I-N-G*c%a%p%y%b%a^r%a@s
1337pr0j3ct
Therefore, if you need to use something like the previous specify a value for your projectName
field.
config:
"config": {
"branchNameCommitModifier": {
"preChar": "{",
"postChar": "}",
"projectName": "TESTPROJECT"
}
current branch name TESTPROJECT-9999
commit command: commit -m "TESTPROJECT-0001 fixing issue 0001."
actual commit message value: "TESTPROJECT-0001 fixing issue 0001."
Note: since you did not include the prefix character or the postfix character it did not include them in the actual commit message.
same config & branch name as before
commit command: commit -m "updated the stuff in the files."
actual commit message value: "{TESTPROJECT-9999} updated the stuff in the files."
config:
"config": {
"branchNameCommitModifier": {
"preChar": "{",
"postChar": "}",
"projectName": "TESTPROJECT"
}
current branch name where am i
commit command: commit -m "idk what im doing lol."
actual commit message value: "{NO-ISSUE} idk what im doing lol."
The commit message value will always take precedence over the branch name value.
If there are any errors during install it may be a permissions issue as the install scripts tries to do the following:
index.js
into the project's .git/hooks/commit-msg
Therefore, if you wish to fix any errors you can try doing the preceding steps manually.
FAQs
This module installs a commit-msg hook that will prepend a project issue number inferred from either the commit message or the current branch name. More details in the examples section below.
The npm package branch-name-commit-modifier receives a total of 1 weekly downloads. As such, branch-name-commit-modifier popularity was classified as not popular.
We found that branch-name-commit-modifier 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
At its inaugural meeting, the JSR Working Group outlined plans for an open governance model and a roadmap to enhance JavaScript package management.
Security News
Research
An advanced npm supply chain attack is leveraging Ethereum smart contracts for decentralized, persistent malware control, evading traditional defenses.
Security News
Research
Attackers are impersonating Sindre Sorhus on npm with a fake 'chalk-node' package containing a malicious backdoor to compromise developers' projects.