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
Hi~
Adding tags for repo could specify points in history and mark release points.
It's helpful for user to know the version and status of repository, and would enable wider distribution of the library, for example on CDNJS
Would you please consider on using tags?
Thanks for your great work!!
Piicksarn
The text was updated successfully, but these errors were encountered:
Using npm version should make the tagging easy to manage as well.
I would consider what is being tagged though, before committing to version tags. This repo currently houses two distinct things, i.e. the nomnoml web application and the nomnoml library (the npm package). It is important to be clear exactly what is being tagged, so that for example changes that only affect the web application doesn't bump the version, but changes to the library part does.
Ideally these two parts should be separated, but that is currently not the case.
Hi~
Adding tags for repo could specify points in history and mark release points.
It's helpful for user to know the version and status of repository, and would enable wider distribution of the library, for example on CDNJS
Would you please consider on using tags?
Thanks for your great work!!
Piicksarn
The text was updated successfully, but these errors were encountered: