Despite being triggered by changes pushed to git all of our builds are now showing Changes (0) on the build summary page after the build completes
This is hampering our QA team because it makes it very hard for them to confirm if a particular fix made it into a particular build.
…and they’re back. That was a weird interlude. Thank you if it was someone on the Unity side fixing it.
We had enabled shallow cloning to reduce build times but have re-enabled full clones while we re-work shallow clones to be more feature rich (config specific rather than project).
