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
In my opinion, there is no reason to not bump a file if Git ignores it. .gitignore does it's job, commit-and-tag-version does (only) it's own. My argument is kind of separations of concerns.
When using commit-and-tag-version, I ran into a bug of bmeck/dotignore (which I don't report as the project seems dead). This bug ultimately led to the package.json in my project not being updated using commit-and-tag-version. My .gitignore had an invalid entry, which made bmeck/dotignore behave inappropriately. But well, the package.json would have still be updated if commit-and-tag-version wouldn't check for .gitignore at all
Is
.gitignore
fileSuggestion
In my opinion, there is no reason to not bump a file if Git ignores it. .
gitignore
does it's job, commit-and-tag-version does (only) it's own. My argument is kind of separations of concerns.Background
.gitignore
had an invalid entry, which made bmeck/dotignore behave inappropriately. But well, the package.json would have still be updated if commit-and-tag-version wouldn't check for .gitignore at allThe text was updated successfully, but these errors were encountered: