Skip to content

Do not run CI on merges to relese #19004

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
Nov 21, 2023

Conversation

Kordyjan
Copy link
Contributor

PRs are merged to the release branches using our own implementation of the merge queue. The history for them is linearised, and we are running all the CI after every backported batch. Those builds are redundant and can clog our runners.

[skip ci]

PRs are merged to the release branches using our own implementation of the merge queue. The history for them is linearised and we are running all the CI both after every backported batch. Those builds are redundant and can clog our runners.
Kordyjan added a commit that referenced this pull request Nov 21, 2023
@Kordyjan Kordyjan merged commit b44a1db into scala:main Nov 21, 2023
@Kordyjan Kordyjan deleted the do-not-run-ci-on-release-merge branch November 21, 2023 10:30
@Kordyjan Kordyjan added this to the 3.4.0 milestone Dec 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant