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
Thanks @christian-draeger for your excellent work on this action. Simple yet effective solution to a common annoyance of setting up automatic versioning.
I quickly noticed that I need to be able to add build number to the version string, so I added the needed logic for that in a forked repo (TLii/increment-semantic-version-with-build-data). All changes are (should be) non-breaking.
Before I open a pull request, do you see this as a feature that should or could be added to the upstream, or shall I keep it a separate fork?
The text was updated successfully, but these errors were encountered:
Hi
Thanks @christian-draeger for your excellent work on this action. Simple yet effective solution to a common annoyance of setting up automatic versioning.
I quickly noticed that I need to be able to add build number to the version string, so I added the needed logic for that in a forked repo (TLii/increment-semantic-version-with-build-data). All changes are (should be) non-breaking.
Before I open a pull request, do you see this as a feature that should or could be added to the upstream, or shall I keep it a separate fork?
The text was updated successfully, but these errors were encountered: