[deepin-wm]

背景

构建类 GitHub Actions 工作流原本在 push 和 pull_request 两个事件下都会运行，主干每次推送都会触发一轮完整构建。按需求，构建类 workflow 只需在 pull_request 下运行，push 触发移除。

改动内容

删除以下构建类 workflow 的 push 触发，仅保留 pull_request：

• .github/workflows/dde-seatd-archlinux-build.yml
• .github/workflows/dde-seatd-debian-build.yml
• .github/workflows/dde-seatd-deepin-build.yml

on: 块只删不加，未新增或改写任何其它触发键。

为什么这么改

构建 workflow 里没有依赖 push 事件的分支逻辑，移除触发不会让任何步骤失效；这些 workflow 也只通过 actions/upload-artifact@v4 上传产物，不做 release/部署/推包，因此对对外产物无影响。

刻意未改动的部分

.github/workflows/backup-to-gitlab.yml 保留 push：它是镜像/备份流程，不属于构建类。cppcheck.yml、call-* 系列本就为 pull_request_target / issue_comment 触发，不含 push。

关联

• Multica Issue: WM-565

Summary by Sourcery

CI:

• Configure the Arch Linux, Debian, and Deepin build workflows to run only for pull requests instead of pull and push events.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

The PR reduces redundant CI builds by making the Arch Linux, Debian, and Deepin build workflows run only for pull requests, removing push-triggered executions without changing workflow steps or delivery-related automation.

File-Level Changes

Change	Details	Files
Restrict the three platform-specific build workflows to pull request events by removing their push triggers.	Delete the push event from each workflow’s on block. Preserve the existing pull_request trigger and all workflow jobs, permissions, and build behavior. Leave non-build workflows and their triggers unchanged.	.github/workflows/dde-seatd-archlinux-build.yml .github/workflows/dde-seatd-debian-build.yml .github/workflows/dde-seatd-deepin-build.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[deepin-ci-robot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[deepin-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: deepin-wm

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

Details

Needs approval from an approver in each of these files:

• debian/deepin/OWNERS

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