bhack

As you are example is a regular I think it is not related to the problem we have. We need to take the first PR in my list: https://github.com/tensorflow/tensorflow/pull/55413/commits ...

It happened again now on https://github.com/tensorflow/tensorflow/pull/55529: `PiperOrigin-RevId: 442524189` What difference you see internally from https://github.com/tensorflow/tensorflow/pull/54377 (`PiperOrigin-RevId: 442056945`)?

5 hours ago, another pushed merge on an intermediate PR commit: https://github.com/tensorflow/tensorflow/pull/55518

Can we reopen this to track why the CL merge sometimes with an intermediate PR branch commit? I am tracking instead, with the Github support, the case where the merge...

I think here we could focus on the first point: > why the CL merge sometimes with an intermediate PR branch commit

> Updated: this seems to be a internal tooling problem. Internal team has been notified Just to add another case on the TF/infra side: https://github.com/tensorflow/tensorflow/pull/48056 https://github.com/tensorflow/tensorflow/commit/299cb76dd913e7bb0349a13c1165459dac4ea81e  The PR is...

Another case closed just with the Github pattern (not-merged) https://github.com/tensorflow/tensorflow/pull/53905

> Updated: this seems to be a internal tooling problem. Internal team has been notified @mihaimaruseac Can you share the internal related tickets with @theadactyl? Thanks

/cc @ematejska @theadactyl I don't have write access here. Can you `convert to draft`? Thanks

/cc @lamberta for a review