Skip to content

CI Fix string comparison in check milestone workflow #19840

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
Apr 7, 2021

Conversation

cmarmo
Copy link
Contributor

@cmarmo cmarmo commented Apr 7, 2021

Reference Issues/PRs

Follow-up of #19833. Thanks @NicolasHug for noticing.
The variable in the comparison was no longer a string.

Cc @thomasjpfan

@thomasjpfan thomasjpfan added this to the 1.0 milestone Apr 7, 2021
@thomasjpfan
Copy link
Member

This did not trigger when I added a milestone.

@thomasjpfan
Copy link
Member

I do not think there is a trigger for "adding a milestone"

@cmarmo
Copy link
Contributor Author

cmarmo commented Apr 7, 2021

I do not think there is a trigger for "adding a milestone"

That's my problem... :) you can add a label if you only need to test

@cmarmo cmarmo added the Bug label Apr 7, 2021
@thomasjpfan
Copy link
Member

thomasjpfan commented Apr 7, 2021

I did not notice this in my first review, this means a maintainer must add a milestone and then add a label to trigger the workflow. (In that order) If there isn't a proper label to add, then we need to add and remove a label to trigger the check milestone workflow.

I'll merge to fix the bug, but I am very uncertain about this milestone check.

@thomasjpfan thomasjpfan merged commit 36c635b into scikit-learn:main Apr 7, 2021
thomasjpfan pushed a commit to thomasjpfan/scikit-learn that referenced this pull request Apr 19, 2021
@glemaitre glemaitre mentioned this pull request Apr 22, 2021
12 tasks
@cmarmo cmarmo deleted the milestone-fix branch August 26, 2022 19:21
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