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
When the command init is run, gommitizen makes a .vesion.json file with a field called commit with a default value of HEAD^1.
That means that gommitizen must check from the previous commit of HEAD to the last commit looking for changes in the bumping process.
Suppose the repository has an older commit with the changes needed to make the bump properly. gommitizen won't find that.
Is there any way to point the field commit to the first git commit when initializing gommitizen? That would solve the problem.
Once the first bump is done properly, the field commit is rewritten with a specific commit and this problem won't occur again. This is just an init problem.
The text was updated successfully, but these errors were encountered:
When the command init is run, gommitizen makes a .vesion.json file with a field called
commit
with a default value ofHEAD^1
.That means that gommitizen must check from the previous commit of HEAD to the last commit looking for changes in the bumping process.
Suppose the repository has an older commit with the changes needed to make the bump properly. gommitizen won't find that.
Is there any way to point the field
commit
to the first git commit when initializing gommitizen? That would solve the problem.Once the first bump is done properly, the field commit is rewritten with a specific commit and this problem won't occur again. This is just an init problem.
The text was updated successfully, but these errors were encountered: