-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
chore: change module name to OpenListTeam/OpenList #2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
jyxjjj
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
直接这样改的话没法跑起来 暂时不用关 有一些地方还有链接双斜杠问题 请修改 然后可以先等子项目发布完
链接问题已修改 |
|
包名当中 v3 感觉没必要保留,可以一并换掉。 |
直接修改应该没问题吧,我在本地测试了,全局替换,然后运行无影响。 |
这个可以 |
This comment was marked as duplicate.
This comment was marked as duplicate.
通常来说,发布release不应该变更包名。毕竟包名是一个全局引用的名字,经常跟随版本改包名,不是一个合理的操作。 |
|
那么包名决定为 |
|
cc @Kuingsmile 进展如何, 先不管包名吧, 发版再说 |
remove v3 in all module name |
OK, let's have conflicts resolved and then squash merge the PR. |
|
如果openlist直接从v1开始发布,那确实应该去掉包名里的/v3,如果以后的版本号从v3开始,那不应该去掉 |
See #2 (comment) |
cc @Kuingsmile How's everything going? |
https://go.dev/doc/modules/version-numbers#major-version 这不是golang中的最佳实践,不带/v4后缀直接发4.x.x版本会让人迷惑 |
只有一些小的冲突了,除了config.yml,这个在合并的时候手动处理下吧,原文件的链接还是指向alist-org/alist的 |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, waiting for CI pass


change module name from alist-org/alist to OpenListTeam/OpenList