A plugin to get Git contributors and create a humans text file. More information about this file and how to create one for knowing whom has contributed to a site, can be found at humanstxt.org.
This plugin requires Grunt ~0.4.1
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 grunt-git-humans --save-dev
One the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:
grunt.loadNpmTasks('grunt-git-humans');
In your project's Gruntfile, add a section named git_humans
to the data object passed into grunt.initConfig()
. The task will respect the git mailmap file in your root, if you decide to use one.
grunt.initConfig({
git_humans: {
options: {
// Task-specific options go here.
},
},
})
Type: String
Default value: './humans.txt'
The default path and filename for the file.
Type: String
Default value: 'master'
A string value that is used to determine what branch the list will be used for the query.
Type: Boolean
Default value: false
A boolean value that allows you to return the list ordered by number of commits.
Type: Boolean
Default value: false
A boolean value that allows you to return the list ordered by latest commits.
Type: Boolean
Default value: false
A boolean value that allows you to use the mailmap file to clean up commit names/emails. This requires git >= 1.8
Type: String
Default value: Empty String
This string will be prepended to the output. Template strings (e.g. <%= config.value %> can be used and are encouraged. If left empty, will add last updated dated.
In this example, the default options are used. No reason to pass anything to create the file at root from the master branch.
grunt.initConfig({
git_humans: {
options: {},
},
})
If you'd like to create the file as a different name for other purposes, or with alternate ordering options then you can do add those easily.
grunt.initConfig({
git_humans: {
options: {
path: 'contributors/custom.txt',
branch: 'master',
byCommits: true
},
},
})
In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using Grunt.
- 2014-03-14 v0.1.0 First release to start initial use on projects
- Add more detailed tests (e.g., testing for git and log results)