phlax

@cainelli needs a main merge /wait

@jwendell i can help - altho not entirely clear what is needed - feel free to ping on slack if its helpful

i think the best thing is to set up github workflows for this historically we used azp for the main build+test jobs, but we are (slowly) transitioning these to github...

re sync - ok - that can be done, esp as its not on our `main` branch (which would create a lot of ci). using a PR rather than just...

thinking further - it also needs to handle conflict if your envoy branch != the upstream one

we have a system setup already for triggering workflows in downstream repos, so triggering whatever workflow is required should be pretty easy

i was looking further at automator.sh - specifically i was trying to figure out how ci was being triggered - afaict that is handled by prow (https://prow.k8s.io/) - which is...

further to what i wrote above - github has just added arm runners, so this should simplify things a lot

PR needs main merge - CI is breaking due to too much change

@yanavlasov i think this is waiting for further review