Skip to content

chore: add which-release script #18657

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 3 commits into from
Jul 1, 2025
Merged

chore: add which-release script #18657

merged 3 commits into from
Jul 1, 2025

Conversation

dannykopping
Copy link
Contributor

This will help us determine what's made it into releases easily.

Example:

$ ./scripts/which-release.sh $(gh pr view 12535 --json mergeCommit | jq '.mergeCommit.oid' -r)
It is recommended that you run `git fetch -ap origin` to ensure you get a correct result.
Commit was found in the following release branches:
  release/2.10
  release/2.11
  release/2.12
  release/2.13
  release/2.14
  release/2.15
  release/2.16
  release/2.17
  release/2.18
  release/2.19
  release/2.20
  release/2.21
  release/2.22
  release/2.22-patch
  release/2.23
  release/2.24

Signed-off-by: Danny Kopping <dannykopping@gmail.com>
Signed-off-by: Danny Kopping <dannykopping@gmail.com>
Signed-off-by: Danny Kopping <dannykopping@gmail.com>
@dannykopping dannykopping enabled auto-merge (squash) July 1, 2025 07:56
@dannykopping dannykopping merged commit 0f56f00 into main Jul 1, 2025
34 checks passed
@dannykopping dannykopping deleted the dk/which-release branch July 1, 2025 08:05
@github-actions github-actions bot locked and limited conversation to collaborators Jul 1, 2025
@stirby
Copy link
Collaborator

stirby commented Jul 3, 2025

This will be helpful, thanks @dannykopping.

Will this catch cherry-picked PRs?

@dannykopping
Copy link
Contributor Author

Afraid not. Cherry-picked commits have different commit hashes even though they contain the same changes, and this tool only uses the commit hashes.

e.g. #18726

$ ./scripts/which-release.sh f97bd76
It is recommended that you run `git fetch -ap origin` to ensure you get a correct result.
Commit was found in the following release branches:
  release/2.24

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants