Skip to content

[release/9.0.1xx] [Github Actions] Remove Branch Lockdown Labels on Branding Merge #48181

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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 9 commits into from
Jun 11, 2025

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Apr 4, 2025

Backport of #47371 to release/9.0.1xx

/cc @edvilme

@marcpopMSFT
Copy link
Member

Note: needs testing before merge

@MiYanni
Copy link
Member

MiYanni commented May 21, 2025

@marcpopMSFT Is there a way to test this?

@edvilme
Copy link
Contributor

edvilme commented May 21, 2025

@MiYanni What I intended on doing before was testing on a forked repo: creating a couple of regular PRs (with branch lockdown label) and a couple of Branding PRs, and seeing if the regular PRs get the label removed.

@MiYanni
Copy link
Member

MiYanni commented Jun 10, 2025

/azp run dotnet-sdk-public-ci,sdk-source-build

Copy link

Azure Pipelines successfully started running 2 pipeline(s).

@MiYanni MiYanni merged commit 39ca42f into release/9.0.1xx Jun 11, 2025
32 checks passed
@MiYanni MiYanni deleted the backport/pr-47371-to-release/9.0.1xx branch June 11, 2025 17:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Infrastructure untriaged Request triage from a team member
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants