You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Before gh-pages I personally knew grunt-bump - used in one of my projects. So they have code, which takes package.json/bower.jsonversion 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:
after grunt gh-pages command I have wrong tag name on my repo:
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
The text was updated successfully, but these errors were encountered:
Before
gh-pages
I personally knewgrunt-bump
- used in one of my projects. So they have code, which takespackage.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 forgh-pages
:after
grunt gh-pages
command I have wrong tag name on my repo: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 withtag
property works fine.--gh-pages-tag
doesn't work. Details here: #55The text was updated successfully, but these errors were encountered: