grunt-git-describe-plus

Describes git commit and push status. Based on grunt-git-describe with addition to detect if locally unpushed changes exist.

Getting Started

This plugin requires Grunt ~0.4.0

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:

1npm install grunt-git-describe-plus --save-dev

One the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:

1grunt.loadNpmTasks('grunt-git-describe-plus');

The "git-describe" task

Overview

In your project's Gruntfile, add a section named git-describe to the data object passed into grunt.initConfig().

1grunt.initConfig({
2  "git-describe": {
3    "options": {
4      // Task-specific options go here.
5    },
6    "your_target": {
7      // Target-specific file lists and/or options go here.
8    },
9  },
10})

Note that since this is a multi-task you have to have at least one target defined for git-describe (otherwise the task won't run)

Options

options.cwd

Type: String
Default value: '.'

A string value that is used to do set the current working directory when spawning the git command

options.commitish

Type: String
Default value: undefined

A string value that is used as commitish for git. Default is to use HEAD.

options.template

Type: String
Default value: {%=tag%}-{%=since%}-{%=object%}{%=dirty%}

A string value used to format the result of this task

options.failOnError

Type: boolean
Default value: true

A boolean that allows Grunt to keep going if there's an error in this task. This is useful if your build isn't guaranteed to always be run from within a Git repo.

Saving Output

If you would like to save or otherwise use the retun value, use grunt.event.emit. Here is an example:

1grunt.registerTask('saveRevision', function() {
2    grunt.event.once('git-describe', function (rev) {
3        grunt.log.writeln("Git Revision: " + rev);
4        grunt.option('gitRevision', rev);
5    });    
6    grunt.task.run('git-describe');
7});

Returned Object

The rev object returned makes several specific properties available, in addition to the full toString description.

1grunt.event.once('git-describe', function (rev) {
2  grunt.log.writeln("Git rev tag: " + rev.tag);
3  grunt.log.writeln("Git rev since: " + rev.since);
4  grunt.log.writeln("Git rev object: " + rev.object); // The 6 character commit SHA by itself
5  grunt.log.writeln("Git rev dirty: " + rev.dirty);   // A flag denoting whether all local changes are committed
6  grunt.log.writeln("Git rev unpushed: " + rev.unpushed);   // A flag denoting whether there are unpushed local changes
7});

Contributing

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.

Release History

2.3.2 - Support CLI options
2.3.1 - Externalize common code to separat modules
2.3.0 - Added support for templated parameters
2.2.0 - Removed support for callback and prop (use grunt.event.emit instead)
2.1.0 - Added support for callback and template and deprecated dirtyMark
2.0.0 - Updated version for grunt ~0.4.0
1.0.0 - First release, compatible with grunt ~0.3.0