Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
For some tasks, I find git show-branch easier to follow than git log. For example, inspecting the history on someone's PR before merging it. git show-branch master topic stops at the first common ...
#4: Post edited
by
Alexei
·
2021-08-27T06:44:06Z (over 3 years ago)
added relevant tag
#3: Post edited
by
ajv
·
2021-08-24T20:50:55Z (over 3 years ago)
- For some tasks, I find `git show-branch` easier to follow than `git log`. For example, inspecting the history on someone's PR before merging it.
- `git show-branch master topic` stops at the first common ancestor, which is usually not what I want. Usually I want to display the same commits that would have been covered by `git log master...topic`, but in a `show-branch` format. Sometimes the two are the same, but not always.
- Is there an incantation that will do this?
[Edit]: After experimenting a bit, it looks like I only run into a problem if the tip of one branch is a merge of the other. For example, consider a history like this:- ```
- master *---*---A---B---*
- \ \
- topic a---b---c---*
- ```
- If I then do `git show-branch master topic`, it doesn't include a, b, and c, even though those commits are not ancestors of master.
- For some tasks, I find `git show-branch` easier to follow than `git log`. For example, inspecting the history on someone's PR before merging it.
- `git show-branch master topic` stops at the first common ancestor, which is usually not what I want. Usually I want to display the same commits that would have been covered by `git log master...topic`, but in a `show-branch` format. Sometimes the two are the same, but not always.
- Is there an incantation that will do this?
- **[Edit]**: After experimenting a bit, it looks like I only run into a problem if the tip of one branch is a merge of the other. For example, consider a history like this:
- ```
- master *---*---A---B---*
- \ \
- topic a---b---c---*
- ```
- If I then do `git show-branch master topic`, it doesn't include a, b, and c, even though those commits are not ancestors of master.
#2: Post edited
by
ajv
·
2021-08-24T20:50:43Z (over 3 years ago)
Add clarification
- For some tasks, I find `git show-branch` easier to follow than `git log`. For example, inspecting the history on someone's PR before merging it.
- `git show-branch master topic` stops at the first common ancestor, which is usually not what I want. Usually I want to display the same commits that would have been covered by `git log master...topic`, but in a `show-branch` format. Sometimes the two are the same, but not always.
Is there an incantation that will do this?
- For some tasks, I find `git show-branch` easier to follow than `git log`. For example, inspecting the history on someone's PR before merging it.
- `git show-branch master topic` stops at the first common ancestor, which is usually not what I want. Usually I want to display the same commits that would have been covered by `git log master...topic`, but in a `show-branch` format. Sometimes the two are the same, but not always.
- Is there an incantation that will do this?
- [Edit]: After experimenting a bit, it looks like I only run into a problem if the tip of one branch is a merge of the other. For example, consider a history like this:
- ```
- master *---*---A---B---*
- \ \
- topic a---b---c---*
- ```
- If I then do `git show-branch master topic`, it doesn't include a, b, and c, even though those commits are not ancestors of master.
#1: Initial revision
by
ajv
·
2021-08-23T21:11:12Z (over 3 years ago)
How do I ask git-show-branch to display a commit range?
For some tasks, I find `git show-branch` easier to follow than `git log`. For example, inspecting the history on someone's PR before merging it. `git show-branch master topic` stops at the first common ancestor, which is usually not what I want. Usually I want to display the same commits that would have been covered by `git log master...topic`, but in a `show-branch` format. Sometimes the two are the same, but not always. Is there an incantation that will do this?