Skip to content
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

On the backports-v1.8 branch, run CI on v1.8 #256

Merged
merged 1 commit into from
Sep 13, 2022

Conversation

dkarrasch
Copy link
Member

Maybe replaces #255?

@rayegun
Copy link
Member

rayegun commented Sep 13, 2022

Should we open a PR to merge backports-release-1.8 => release-1.8 with this in it? That should trigger CI right?

@dkarrasch
Copy link
Member Author

backports-release-1.8 => release-1.8

Yes. We could do that right away, or include the vcat fix before that. But I guess the order doesn't matter much as long as we don't change the commit SHA in Julia release-v1.8, right?

@dkarrasch
Copy link
Member Author

I'm merging this. It can't be wrong to do that IIUC.

@rayegun
Copy link
Member

rayegun commented Sep 13, 2022

change the commit SHA in Julia release-v1.8, right?

Yeah I say we merge into backports and just open a PR for CI purposes. Once we've done that and it passes we can follow up with Kristoffer or Dilum to be absolutely sure we've got it right.

@dkarrasch dkarrasch merged commit 2cae325 into backports-release-1.8 Sep 13, 2022
@dkarrasch dkarrasch deleted the dkarrasch-patch-2 branch September 13, 2022 17:54
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.

2 participants