1. I try to check github web interface. Usually it show the pr where this change is present.
2. I try to go by this link:
Thanks github, but it's a wrong repo...
3. I try to go to gitlab:
Well, nothing...
4. I try to use git:
Code: Select all
git log --graph --format=tformat:'%C(yellow)%h %C(cyan)%aN %C(blue bold)%ar%Creset%Cred%d%Creset %s'
I wan't able to track this line until it merges master...
5. How about more specific tool?
https://stackoverflow.com/questions/847 ... fic-commit
Code: Select all
$ pip3 install --user git-get-merge
$ git-get-merge 1b8d500c0
Might be either of:
commit 31c68c534ca62493d08a3bc6d8e02178eceb4dc9
Merge: c3d7ee5a9 24078d4a7
Author: Miloslav Číž <[email protected]>
Date: Thu Jun 14 13:23:23 2018 +0200
Merge branch 'drummyfish/openmw-toggleborders'
commit 5a9e382efe04960e1bed3a309c81ca3d7fc7a1b4
Merge: ccfc07e7e 2a23b5351
Author: Marc Zinnschlag <[email protected]>
Date: Fri Jun 15 12:23:08 2018 +0200
Merged pull request #1421
6. And the last one try:
Code: Select all
$ git rev-list 1b8d500c0..master --ancestry-path --format=tformat:'%h %aN %s' > ancestry-path.log
$ git rev-list 1b8d500c0..master --first-parent --format=tformat:'%h %aN %s' > first-parent.log
$ diff ancestry-path.log first-parent.log | wc -l
4284
So my proposal is to rebase pull requests (merge requests) before merge into master. If pr doesn't have conflicts and has 1-5 commits probably it's fine to merge as is. But if pr contains commits like merge from master and has a several month lifetime then just to make the commits history more clear it should be rebased right before the merge.
For now my only hypothesis about that commit is it was pushed without pr right into master. I'd appreciate if someone will find how did it end up in master. That's another concern. We shouldn't push commits right to the master without pr. I see sometimes such changes. Github allows to forbid such pushes for all users or except admins. We need to sync with gitlab, so I assume admins should be allowed to do this.