Skip to content

🤖 Pick PR #61978 (Restructure CI to prepare for requi...) into release-5.9 #62164

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 1 commit into from
Aug 1, 2025

Conversation

typescript-bot
Copy link
Collaborator

This cherry-pick was triggered by a request on #61978.

Please review the diff and merge if no changes are unexpected.

Copy link
Member

@weswigham weswigham left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this even actually need to be ported to a branch? I thought main was the source of truth for all branches of CI.

@github-project-automation github-project-automation bot moved this from Not started to Needs merge in PR Backlog Aug 1, 2025
@jakebailey
Copy link
Member

No, CI runs per branch so release branches run old stuff.

I could make only main have required checks and the merge queue, but on the cherry-pick you were looking for the "merge when ready" button which would require the required checks, so, probably okay to do.

@jakebailey jakebailey merged commit 0d9b9b9 into release-5.9 Aug 1, 2025
32 checks passed
@github-project-automation github-project-automation bot moved this from Needs merge to Done in PR Backlog Aug 1, 2025
@jakebailey jakebailey deleted the cherry-pick/61978/release-5.9 branch August 1, 2025 05:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

4 participants