ci: split Qt5 and Qt6 workflow steps#631
Open
zccrs wants to merge 1 commit into
Open
Conversation
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
Split the Arch Linux source-build steps by Qt5 and Qt6 to mirror dtkcore workflow handling. Also make the Deepin matrix step names explicitly mention the Qt version so the CI flow is easier to read and debug.
zccrs
force-pushed
the
fix/workflow-qt-split
branch
from
8dcdca8 to
3450729
Compare
Member
Author
|
已按 dtkcore#564 的方式把 workflow 中 Qt5 / Qt6 路径明确拆开：
当前这版 PR 的 GitHub Actions 已全部通过。 |
Contributor
|
TAG Bot New tag: 6.7.43 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary\n- split Arch Linux workflow source-build steps by Qt5/Qt6 like dtkcore#564\n- add Qt-version-specific step names in Deepin workflow to make the matrix intent explicit\n- keep the existing test behavior so the workflow remains green\n