Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

[release/9.0-staging] Add workflow to prevent merging a PR when theNO-MERGE label is applied#111961

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Conversation

@github-actions
Copy link
Contributor

@github-actionsgithub-actionsbot commentedJan 29, 2025•
edited by carlossanlop
Loading

Backport of#111940 to release/9.0-staging

Infra only. Workflow that already works onmain that prevents merging a PR when theNO-MERGE label is applied.

Edit - Confirmed it works in this PR:

image

@ghostghost added the needs-area-labelAn area label is needed to ensure this gets routed to the appropriate area owners labelJan 29, 2025
@carlossanlopcarlossanlop added Servicing-approvedApproved for servicing release area-Infrastructure and removed needs-area-labelAn area label is needed to ensure this gets routed to the appropriate area owners labelsJan 29, 2025
@carlossanlopcarlossanlop self-assigned thisJan 29, 2025
@carlossanlopcarlossanlop added the NO-MERGEThe PR is not ready for merge yet (see discussion for detailed reasons) labelJan 29, 2025
@dotnet-policy-service
Copy link
Contributor

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info inarea-owners.md if you want to be subscribed.

@carlossanlopcarlossanlop removed the NO-MERGEThe PR is not ready for merge yet (see discussion for detailed reasons) labelJan 29, 2025
@carlossanlopcarlossanlop requested a review froma teamJanuary 29, 2025 18:56
@danmoseleydanmoseley added NO-MERGEThe PR is not ready for merge yet (see discussion for detailed reasons) and removed NO-MERGEThe PR is not ready for merge yet (see discussion for detailed reasons) labelsJan 29, 2025
@carlossanlop
Copy link
Contributor

I see the utility of having this in servicing for now. The change was easy to make and we can temporarily have it here while we work on the arcade solution for everyone. When that happens, and we backport it to 9.0 and 8.0 in arcade, we can then remove this runtime-specific workflows to use the arcade one instead.

@carlossanlopcarlossanlop merged commit62d433f intorelease/9.0-stagingJan 29, 2025
30 of 35 checks passed
@carlossanlopcarlossanlop deleted the backport/pr-111940-to-release/9.0-staging branchJanuary 29, 2025 19:15
@github-actionsgithub-actionsbot locked and limited conversation to collaboratorsMar 1, 2025
Sign up for freeto subscribe to this conversation on GitHub. Already have an account?Sign in.

Reviewers

@jkoritzinskyjkoritzinskyjkoritzinsky approved these changes

Assignees

@carlossanlopcarlossanlop

Labels

area-InfrastructureServicing-approvedApproved for servicing release

Projects

Status: Done

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@carlossanlop@jkoritzinsky@danmoseley
[8]ページ先頭
©2009-2025 Movatter.jp