Skip to content
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

重构编译工作流文件 #4009

Merged
merged 9 commits into from
Jun 13, 2024
Merged

重构编译工作流文件 #4009

merged 9 commits into from
Jun 13, 2024

Conversation

allMagicNB
Copy link
Contributor

@allMagicNB allMagicNB commented Jun 11, 2024

我个人认为并没有必要要多一个友好名称……
增加上传文件名带版本 tag - Commit 次数 - g + 提交 Short Hash,然后……先等等吧,看看有没啥好的意见,可以去#3987 或下方 Comment,我觉得能做的话会加进#3987 里面,然后把此 PR 标记为 Draft。

@allMagicNB allMagicNB requested a review from LTCatt June 11, 2024 22:14
.github/workflows/build.yml Outdated Show resolved Hide resolved
.github/workflows/build.yml Outdated Show resolved Hide resolved
@allMagicNB allMagicNB requested a review from 3gf8jv4dv June 12, 2024 05:33
@LTCatt
Copy link
Member

LTCatt commented Jun 12, 2024

你也没必要把人家的注释都删了吧……

@Silverteal
Copy link
Contributor

下次在有相同主题的PR还Open的时候,建议优先给那个PR的分支发PR,这样不用处理冲突……

@allMagicNB
Copy link
Contributor Author

下次在有相同主题的PR还Open的时候,建议优先给那个PR的分支发PR,这样不用处理冲突……

你说得不对,因为那样直接合并的话你的成果就废了。

@allMagicNB
Copy link
Contributor Author

allMagicNB commented Jun 12, 2024

你也没必要把人家的注释都删了吧……

这是重构,只不过文件名和部分代码重复了而已(

.github/workflows/build.yml Outdated Show resolved Hide resolved
@allMagicNB
Copy link
Contributor Author

@3gf8jv4dv How about looking at the file name now?

@allMagicNB allMagicNB requested a review from 3gf8jv4dv June 12, 2024 14:15
@3gf8jv4dv
Copy link
Collaborator

@3gf8jv4dv How about looking at the file name now?

Now this looks great!

By the way, I have seen the format you wrote in other projects, but I just remembered it when I saw it just now, lol.

Copy link
Member

@LTCatt LTCatt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

把一些不太废话的注释加回来吧……

@Silverteal
Copy link
Contributor

下次在有相同主题的PR还Open的时候,建议优先给那个PR的分支发PR,这样不用处理冲突……

你说得不对,因为那样直接合并的话你的成果就废了。

Git的文本引擎可以按行合并,而且您可以从分支的仓库拉取进行修改,这样就不会出现上述情况。

@allMagicNB
Copy link
Contributor Author

allMagicNB commented Jun 13, 2024

把一些不太废话的注释加回来吧……

没啥用。
工作流文件就只有四五十行,其中还有很多空行,相信懂 Action 怎么写的都能看懂,要加的话也得后期维护再多到一百多行再加,但是这不可能……

@allMagicNB allMagicNB requested a review from LTCatt June 13, 2024 11:30
@LTCatt
Copy link
Member

LTCatt commented Jun 13, 2024

把已有的注释给删了并没有让东西变得更好,并且也是对其他人的不尊重。不要这样做。

@allMagicNB
Copy link
Contributor Author

allMagicNB commented Jun 13, 2024

我没删我直接给重构的……你不信你去看 Commit 历史。

@LTCatt
Copy link
Member

LTCatt commented Jun 13, 2024

唉,行吧……

@LTCatt LTCatt merged commit f1fedfc into Hex-Dragon:main Jun 13, 2024
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
· 优化 完成 已被处理,将在下次更新之后生效
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants