Philip Durbin 🚀 (May 15 2024 at 14:22): Philip Durbin 🚀 (May 15 2024 at 14:22):For core Dataverse, I often use the query is:pr is:merged no:milestone to find pull requests that have been merged but haven't been assigned a milestone. Then I assign a milestone to them. Are we ok with doing the same for pyDataverse? Here's the query: https://github.com/gdcc/pyDataverse/pulls?q=is%3Apr+is%3Amerged+no%3Amilestone
Philip Durbin 🚀 (May 15 2024 at 14:26):Using https://github.com/gdcc/pyDataverse/pull/1 as an example, I go to commits with the PR like this: https://github.com/gdcc/pyDataverse/pull/1/commits/96d476e5584e4901087ee57ac56d672ccc97e1e4
The oldest tag is v0.1.0 so I would assign that milestone.
Philip Durbin 🚀 (Aug 27 2024 at 14:00):I did my usual is:pr is:merged no:milestone query and gave these two PRs the 0.3.4 milestone:
Jan Range (Aug 27 2024 at 14:29):Great, thanks! That helps :-)
Last updated: Nov 01 2025 at 14:11 UTC