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
Update milestone check script #5938
Conversation
We still cannot retrieve more than 250 commits for a PR, so exceptionally large PRs such as jupyterlab#5508 will still need some special-casing.
More PRs to check that may need to be moved to the 1.0 milestone: c0a8595 Merge pull request #5596 from skurt23/input-styling |
More PRs added: Option to create new markdown file from Launcher and File > New #5511 |
Okay, I think I cleaned up the PRs. Some PRs I had to unset from the 1.0 milestone and then set them again, which was weird. Current script output is: WARNING: PR 5508 (merge d158501) has 410 commits, but GitHub is only giving us 250 of them Congratulations! All PRs in this milestone have commits in the commit history for this version range, so they all probably belong in this milestone. The following commits are not included in any PR on this milestone. be6b55d |
query test($milestone: Int!) { | ||
repository(owner:"jupyterlab" name:"jupyterlab") { | ||
milestone(number:$milestone) { | ||
query test($cursor: String) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ooh, I didn't realize we were using the new graphql based github api!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's been a fun exploration.
This script is used in the release process to check that the milestone correctly reflects what is in the commit history.
WIP since there still needs to be some special-casing for PRs with more than 250 commits (such as #5508).