I think there's no reason to save the traces in the repo, instead, both the old and the newly generated traces can live on s3, which will make it easier to handle as they are in the same place and it will not require us to push into git every time we want to update the traces.
I think there's no reason to save the traces in the repo, instead, both the old and the newly generated traces can live on s3, which will make it easier to handle as they are in the same place and it will not require us to push into git every time we want to update the traces.