Can you either update go1 tag to point to latest stable version (I'm guessing 39104c78546f11be4bbc161e39858258aac6d9b8), or simpler yet, remove it and let master be the latest go gettable version. You can use feature branches for development and merge them into master when they're ready.
I'm guessing this was an unintended situation, but please let me know if that's not the case. Thanks.
Hi,
Currently, your
go1
tag points to commit ce86f93. So when someone doesgo get -u github.com/mattn/go-runewidth
, it will check out that revision.However, you have newer commits that add
Truncate
and fix bugs on master, that are not available:https://github.com/mattn/go-runewidth/compare/go1...master
Can you either update
go1
tag to point to latest stable version (I'm guessing 39104c78546f11be4bbc161e39858258aac6d9b8), or simpler yet, remove it and let master be the latestgo get
table version. You can use feature branches for development and merge them into master when they're ready.I'm guessing this was an unintended situation, but please let me know if that's not the case. Thanks.