On Wed, Oct 9, 2024, at 20:04, Amith Ashok wrote: > Hi , > > I wanted to report a git bug that I encountered today . > > I created a feature branch from a release branch before my peer > committed to it . My peer committed to this branch through the lower > branches of auto merge option to this high branch . > > However when I do a git pull I was facing the issue in of the files. What issue? Usually a git(1) bug can be reproduced with a set of commands (reproduction). And some part of the output demonstrates that there is a bug. Which could be: - The output itself tells you it’s a `BUG` (code path that should be unreachable) - The output or behavior is unreasonable or unexpected given the context Then you provide it here in the bug report. Like: ``` BUG: this should never happen but it did (<file>:<line>) ``` There’s also git-bugreport(1) which you can use to fill out such a report. That will record things like your Git version and other relevant system info. > I tried multiple ways to debug this but ultimately found that the > issue is with got itself . > > I took the a fresh branch from this branch (post merge of my friend ) > then the error does not occur. > > > I appreciate if you look into this . And if this indeed is an issue > could you fix it and you acknowledge my original receipt as the > findings to this . It is standard to credit bug reporters in this project. > > > Thanks > Amith Ashok Chugani -- Kristoffer Haugsbakk
