Repo state leakage

[joe-needham]

Hi,

I did a quick check to see if there was a similar leakage issue as was highlighted here: SWE-bench/SWE-bench#465

I used the image jefzda/sweap-images:gravitational.teleport-gravitational__teleport-82185f232ae8974258397e121b3bc2ed0c3729ed-v626ec2a48416b10a88641359a169d99e935ff03.

This repo is currently checked out at this commit from May 7.

commit ad00c6c789bdac9b04403889d7ed426242205d64 (HEAD)
Author: Andrej Tokarčík <andrej@goteleport.com>
Date:   Fri May 7 13:54:08 2021 +0200
Introduce ClusterNetworkingConfig extracting fields from ClusterConfig (#6638)

Running git log --all, you can see multiple branches on the remote in the future

commit a4aeb26a7c154a0c1da321848922b448ff34bbb2 (origin/jeff/log-undetectable-app-proto)
Author: Jeff Anderson <jeff@goteleport.com>
Date:   Fri Jun 6 16:19:00 2025 -0400
Log if the no protocol detected for any port

While I haven't checked if its possible to deduce the gold-patch from these future commits, it seems plausible that this could happen in some cases.

[jeff-da]

Hey Joe, thanks for the pointer. The main branch should not have future commits, but other branches may have commits in the future. We haven't seen this happening in any of our trajectories, we'll look into removing any future commits too