- You can configure the auto-generated changelog to exclude users (e.g. dependabot) and labels[1]

- The automated changelog is based on PR titles, which allows you to edit them without rewriting history, and labelling them for filtering/grouping.

[1] https://docs.github.com/en/repositories/releasing-projects-o...

Those details should definitely have been a part of the blog post!

…which is nice, when the master is not tagged and you’re trying to find out “does this release include the bug fix in pr #123” (without cloning and/or jumping between tags/branches).

There's already a "compare" selector on the current/old releases page that lets you do just that with two clicks.

Thank you, that is useful, but basically same as "jumping" between branches.

@pronik's reply was spot on, viewing the merge commit, which shows which branches and tags the commit is included in. Example: https://github.com/openshift/okd/commit/e278fba2d8a5aea6b7bd...

Which is extremely easy: you click on the actual patch that has been merged and look under the commit message where all the tags containing this particular commit are shown.

Thank you. Tried on the commit in PR, did not show up, but the merge commit did.

I guess it's dependent on merge strategy, where squash merge will not include the initial commit hash. Or maybe "pr commit view" excludes the same info.