Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

'v%VERSION' support? #56

Open
alundiak opened this issue Jan 22, 2016 · 0 comments
Open

'v%VERSION' support? #56

alundiak opened this issue Jan 22, 2016 · 0 comments

Comments

@alundiak
Copy link

Before gh-pages I personally knew grunt-bump - used in one of my projects. So they have code, which takes package.json/bower.json version and use it for commit/tagName purpose. I thought, it's default behavior/scope of npm/nodejs/grunt to see that %VERSION%, and as result of configs for gh-pages:

'gh-pages':{
            options: {
                base: 'gh-gh',
                tag:'v%VERSION%'
            },
            src: '**'
        }

after grunt gh-pages command I have wrong tag name on my repo:
image

Is it possible to adopt such behavior here in gh-pages?
Every commit of gh-pages should not go with the tag increasing aka bumping. But it can be configurable, like --use-tag-this-time=true or similar.

Note: gh-pages config with tag property works fine. --gh-pages-tag doesn't work. Details here: #55

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant