Skip to content

sync: from linuxdeepin/dtkwidget#141

Closed
deepin-ci-robot wants to merge 1 commit intomasterfrom
sync-pr-663-nosync
Closed

sync: from linuxdeepin/dtkwidget#141
deepin-ci-robot wants to merge 1 commit intomasterfrom
sync-pr-663-nosync

Conversation

@deepin-ci-robot
Copy link
Contributor

Synchronize source files from linuxdeepin/dtkwidget.

Source-pull-request: linuxdeepin/dtkwidget#663

Synchronize source files from linuxdeepin/dtkwidget.

Source-pull-request: linuxdeepin/dtkwidget#663
@deepin-ci-robot
Copy link
Contributor Author

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: deepin-ci-robot

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@deepin-ci-robot
Copy link
Contributor Author

deepin pr auto review

关键摘要:

  • .reuse/dep5文件中添加了VERSIONFiles列表,但未提供上下文说明为什么需要包含VERSION文件。
  • .syncexclude文件中添加了VERSION到排除列表,这可能是为了防止VERSION文件被同步到其他位置。
  • CMakeLists.txt文件中,通过读取VERSION文件来设置DTK_VERSION,这是一个合理的做法,但需要确保VERSION文件的内容格式正确且一致。
  • 新增的VERSION.in文件中使用了@version@占位符,这通常用于构建系统(如CMake)来替换为实际的版本号。

是否建议立即修改:

  • 是,需要提供更多上下文说明为什么需要包含VERSION文件,以及确保VERSION文件的内容格式正确且一致。
  • 是,如果VERSION文件的内容格式不正确或不一致,可能会导致构建失败或运行时错误。
  • 否,新增的VERSION.in文件的使用是合理的,只要确保构建系统正确处理占位符即可。

@deepin-bot
Copy link
Contributor

deepin-bot bot commented Jun 19, 2025

TAG Bot

New tag: 6.0.37
DISTRIBUTION: unstable
Suggest: synchronizing this PR through rebase #146

@deepin-bot
Copy link
Contributor

deepin-bot bot commented Jun 27, 2025

TAG Bot

New tag: 6.0.38
DISTRIBUTION: unstable
Suggest: synchronizing this PR through rebase #148

@deepin-bot
Copy link
Contributor

deepin-bot bot commented Jul 3, 2025

TAG Bot

New tag: 6.0.39
DISTRIBUTION: unstable
Suggest: synchronizing this PR through rebase #152

@18202781743 18202781743 closed this Jul 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants