gnag
gnag copied to clipboard
Gnag comments with incorrect PR SHA if 1+ new commits were added between build starting and Gnag reporting
Expected: comments reported as applying to SHAs 3623c3b then 005ef31. Actual: comments reported as applying to SHA 005ef31 both times.
An improved solution would be to pull the PR HEAD SHA ASAP in the Gnag build. May also be possible to capture a CI env var with this information (which would be much more robust). Maybe we add a new entry in the Gnag configuration block to allow this?