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

Remove unused code #3729

Merged
merged 1 commit into from
Jul 1, 2023
Merged

Remove unused code #3729

merged 1 commit into from
Jul 1, 2023

Conversation

durban
Copy link
Contributor

@durban durban commented Jul 1, 2023

It's private, and nothing uses it.

@durban durban changed the base branch from series/3.x to series/3.5.x July 1, 2023 11:24
@durban durban marked this pull request as ready for review July 1, 2023 12:14
Copy link
Member

@armanbilge armanbilge left a comment

Choose a reason for hiding this comment

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

thanks!

@armanbilge
Copy link
Member

oh, actually whenever you change the base branch, you have to re-trigger CI. the current ✅ is based on CI running against 3.x, not 3.5.x

@armanbilge armanbilge closed this Jul 1, 2023
@armanbilge armanbilge reopened this Jul 1, 2023
@durban
Copy link
Contributor Author

durban commented Jul 1, 2023

Huh, great. Cirrus didn't seem to restart with the close/open, so I tried to restart it manually. I don't know if I succeeded...

@armanbilge
Copy link
Member

Ah, actually Cirrus doesn't need to be restarted anyway ...

So the difference is that GHA CI runs on a synthetic merge commit. So for example, the initial CI run was on 4ef1966 which merged in series/3.x. The close-reopen dance causes CI to run on a new merge commit bfd7630, this time with series/3.5.x.

Meanwhile, Cirrus runs CI on the branch itself, not a synthetic merge commit. So in both cases it is running on 907b121, it doesn't matter which branch the PR is targeting.

@armanbilge armanbilge merged commit c010cb6 into typelevel:series/3.5.x Jul 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants