From 7639c93baffc820f9f19ab1f9d1c085b0b45e071 Mon Sep 17 00:00:00 2001 From: Tyler Yahn Date: Wed, 16 Apr 2025 08:26:29 -0700 Subject: [PATCH] Update the milestone issue search URL (#6651) Add search for issues ... - closed because they were completed - are not labeled "Stale" - have a linked PR showing work was done to complete the issue --- RELEASING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/RELEASING.md b/RELEASING.md index 45274ca27..7c1a9119d 100644 --- a/RELEASING.md +++ b/RELEASING.md @@ -132,7 +132,7 @@ Importantly, bump any package versions referenced to be the latest one you just Once a release is made, ensure all issues that were fixed and PRs that were merged as part of this release are added to the corresponding milestone. This helps track what changes were included in each release. -- To find issues that haven't been included in a milestone, use this [GitHub search query](https://github.com/open-telemetry/opentelemetry-go/issues?q=is%3Aissue%20no%3Amilestone%20is%3Aclosed%20sort%3Aupdated-desc). +- To find issues that haven't been included in a milestone, use this [GitHub search query](https://github.com/open-telemetry/opentelemetry-go/issues?q=is%3Aissue%20no%3Amilestone%20is%3Aclosed%20sort%3Aupdated-desc%20reason%3Acompleted%20-label%3AStale%20linked%3Apr) - To find merged PRs that haven't been included in a milestone, use this [GitHub search query](https://github.com/open-telemetry/opentelemetry-go/pulls?q=is%3Apr+no%3Amilestone+is%3Amerged). Once all related issues and PRs have been added to the milestone, close the milestone.