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

Fix set-milestone failure when latest milestone is closed #15054

Merged
merged 1 commit into from
Nov 18, 2022

Conversation

hashhar
Copy link
Member

@hashhar hashhar commented Nov 16, 2022

Description

There can be situation where the latest milestone is closed but there are still some PRs for which this workflow is pending. The API by default only lists open milestones. This commit changes it to list all milestones so that even if the target milestone is closed it can be found and the PR added to it.

Non-technical explanation

Fix occasional set-milestone failure.

Release notes

(x) This is not user-visible or docs only and no release notes are required.

There can be situation where the latest milestone is closed but there
are still some PRs for which this workflow is pending. The  API by
default only lists open milestones. This commit changes it to list all
milestones so that even if the target milestone is closed it can be
found and the PR added to it.
@cla-bot cla-bot bot added the cla-signed label Nov 16, 2022
@hashhar
Copy link
Member Author

hashhar commented Nov 16, 2022

I'll test this on my fork if possible. It should work though.

@hashhar
Copy link
Member Author

hashhar commented Nov 18, 2022

No easy way to test but I did test the API manually and it's possible to add things to closed milestones.

I'll keep an eye in case of failures, merging this.

@hashhar hashhar merged commit c38490b into trinodb:master Nov 18, 2022
@hashhar hashhar deleted the hashhar/improve-milestone branch November 18, 2022 13:09
@hashhar hashhar added the no-release-notes This pull request does not require release notes entry label Nov 18, 2022
@hashhar hashhar added this to the 404 milestone Nov 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla-signed no-release-notes This pull request does not require release notes entry
Development

Successfully merging this pull request may close these issues.

4 participants