Skip to content

auto integration linuxdeepin/treeland#4202

Open
deepin-community-ci-bot[bot] wants to merge 1 commit into
masterfrom
auto-integration-28344999469
Open

auto integration linuxdeepin/treeland#4202
deepin-community-ci-bot[bot] wants to merge 1 commit into
masterfrom
auto-integration-28344999469

Conversation

@deepin-community-ci-bot

Copy link
Copy Markdown
Contributor

auto integration from pr linuxdeepin/treeland#1063.

Signed-off-by: github-actions <github-actions@users.noreply.github.com>
@github-actions

Copy link
Copy Markdown

RepoTagCheck Bot

Listed repo integration are not modified changelog:

repo tagOrsha
linuxdeepin/treeland 4ef6c19be54267787cc1b70e3d13979c07bf55ce

@github-actions

Copy link
Copy Markdown

INTEGRATION Bot

Integration Details: chore: bump version to 0.8.13 by wineee@linuxdeepin/treeland by deepin-community-ci-bot[bot]

@github-actions

Copy link
Copy Markdown

IntegrationProjector Bot
Deepin Testing Integration Project Manager Info
IssueID: 13512
ProjectItemID: PVTI_lADOABhNec4AL0JezgxGI7E
IssueAddr: linuxdeepin/developer-center#13512

@deepin-ci-robot

Copy link
Copy Markdown
Contributor

Hi @deepin-community-ci-bot[bot]. Thanks for your PR.

I'm waiting for a deepin-community member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants