Update Envoy SHA to point to same commit in istio/envoy:release-1.3

[rlenglet]

This PR updates the Envoy SHA in istio/proxy:release-1.3 to refer to the istio:envoy:release-1.3 branch. The referred commit in unchanged, so it shouldn't have any functional effects.

All subsequent changes to the Envoy SHA must keep referring to commits in the istio:envoy:release-1.3 branch.

[PiotrSikora]

What kind of shenanigans is this? This commit SHA doesn't point to istio/envoy:release-1.3.

[rlenglet]

What kind of shenanigans is this? This commit SHA doesn't point to istio/envoy:release-1.3.

The history of istio/envoy:release-1.3 includes 3f90336c39250c472cfd51b157c305582b7a6725, due to my merge in istio/envoy#90.
Grep for 3f90336 on https://github.com/istio/envoy/commits/release-1.3.

[PiotrSikora]

What kind of shenanigans is this? This commit SHA doesn't point to istio/envoy:release-1.3.

The history of istio/envoy:release-1.3 includes 3f90336c39250c472cfd51b157c305582b7a6725, due to my merge in istio/envoy#90.
Grep for 3f90336 on https://github.com/istio/envoy/commits/release-1.3.

Commit istio/envoy@3f90336 was MERGED into istio/envoy@release-1.3 branch, but it was never a commit ON the istio/envoy@release-1.3 branch.

Try:

$ git checkout release-1.3
$ cat CODEOWNERS
* @istio/release-managers-1-3

$ git checkout 3f90336c39250c472cfd51b157c305582b7a6725
$ cat CODEOWNERS
# TODO(zuercher): determine how we want to deal with auto-assignment
# By default, @envoyproxy/maintainers own everything.
#*       @envoyproxy/maintainers
...
(omitted rest of the output)

If you want to checkout commit istio/envoy@3f90336 in a istio/envoy@release-1.3 branch, then you need to checkout the merge commit, i.e. istio/envoy@ad234fe, or one of the child commits:

$ git checkout ad234fe02c153a8523c95de6d8748a95b023fbe5
$ cat CODEOWNERS
* @istio/release-managers-1-3