6 ms·
…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 b
by arve0 5y ago
…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).
- krono 5y agoThere's already a "compare" selector on the current/old releases page that lets you do just that with two clicks.
- arve0 5y agoThank 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/e278fba2d8a5aea6b7bd2636dce548f8d3463e11 https://github.com/openshift/okd/commit/e278fba2d8a5aea6b7bd...
- pronik 5y agoWhich 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.
- arve0 5y agoThank 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.