
Product
Reachability for Ruby Now in Beta
Reachability analysis for Ruby is now in beta, helping teams identify which vulnerabilities are truly exploitable in their applications.
changelog-customizable
Advanced tools
A grunt task to generate changelog from git repository. Based on grunt-changelog project.
This plugin requires Grunt ~0.4.5
If you haven't used Grunt before, be sure to check out the Getting Started guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:
npm install changelog-customizable --save-dev
Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:
grunt.loadNpmTasks('changelog-customizable');
In your project's Gruntfile, add a section named changelog_customizable to the data object passed into grunt.initConfig().
grunt.initConfig({
changelogcustomizable: {
options: {
// Task-specific options go here.
},
your_target: {
// Target-specific file lists and/or options go here.
},
},
});
Type: String
Default value: null
A string value that is a date or a git tag
Type: String
Default value: null
A string value that is a date or a git tag
Type: String
Default value: 'Changelog'
A string value that is put as generated file's header
Type: Object
Default value: see usage examples
A object to describe destination file
Type: String
Default value: 'dev'
A string to define what kind of changelog to generate. This string should correspond to one of your options.templates regex key (see usage examples) In usage examples we use two different keys, 'dev' and 'release' and each one have a different regex to find commits. If you want to generate all changelog, put 'all' in this property.
Type: String
Default value: empty
A string to determine if we add changelog to destination file or if we erase content. Can be :
Type: String
Default value: automatically generated
Defines the global template of generated file. If not specified the default value is automatically generated with options.templates. In most cases you don't really need to explicitly specified a value in this field. It accepts a template like the following :
{{> features}}{{> fixes}}
Type: Object
Default value: see Usage examples
Defines all templates needed to generate your file.
grunt.initConfig({
changelogcustomizable: {
changelog: {
options: {
start: null,
end: null,
header: 'Changelog',
dest: {
dir: './release-notes/',
fileName: 'changelog',
extension: 'md'
},
type: 'dev',
templates: {
features: {
regex: {
dev: /^(.*)feature(.*)$/gim,
release: /^(.*)release(.*)feature(.*)$/gim
},
template: '##FEATURE:\n\n{{#if features}}{{#each features}}{{> feature}}{{/each}}{{else}}{{/if}}\n'
},
feature: {
template: '\t{{{this}}}\n'
},
fixes: {
regex: {
dev: /^(.*)fixes #\d+:?(.*)$/gim,
release: /^(.*)release(.*)fixes #\d+:?(.*)$/gim
},
template: '##FIXES:\n\n{{#if fixes}}{{#each fixes}}{{> fix}}{{/each}}{{else}}{{/if}}\n'
},
hotfixes: {
regex: {
dev: /^(.*)hotfix #\d+:?(.*)$/gim
},
template: '##HOT FIXES:\n\n{{#if hotfixes}}{{#each hotfixes}}{{> fix}}{{/each}}{{else}}{{/if}}\n'
},
fix: {
template: '\t{{{this}}}\n'
}
}
}
}
});
will generate the following file :
#Changelog
##FEATURE:
first changelog generation with basic options
commit readme and configuration files
##FIXES:
first fix
second fix
Any help is welcome :)
FAQs
A grunt task to generate changelog from git repository.
We found that changelog-customizable 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.

Product
Reachability analysis for Ruby is now in beta, helping teams identify which vulnerabilities are truly exploitable in their applications.

Research
/Security News
Malicious npm packages use Adspect cloaking and fake CAPTCHAs to fingerprint visitors and redirect victims to crypto-themed scam sites.

Security News
Recent coverage mislabels the latest TEA protocol spam as a worm. Here’s what’s actually happening.