Hi everyone, Weihua Hu [1] notified me of a section in Flink's Azure Pipeline documentation [2] where it's suggested to create PRs against flink-ci/mirror as a workaround if you're not having a private Azure Pipeline account and want to run CI with your code changes. Even though it's a viable solution it does generate noise in the Slack channel for build failure (#builds). Additionally, I don't see any extra value in comparison to using your own fork and creating a PR on your branch against the apache/flink repo. CI will be picked up by Flink's CiBot. Or am I missing something?
I couldn't find any ML discussion on that matter. I suggest removing this section in the docs. Best, Matthias [1] https://github.com/flink-ci/flink-mirror/pull/16#issuecomment-1451183958 [2] https://cwiki.apache.org/confluence/display/FLINK/Azure+Pipelines#AzurePipelines-AzurePipelineUsageRestrictions -- [image: Aiven] <https://www.aiven.io> *Matthias Pohl* Opensource Software Engineer, *Aiven* matthias.p...@aiven.io <i...@aiven.io> | +49 170 9869525 aiven.io <https://www.aiven.io> | <https://www.facebook.com/aivencloud> <https://www.linkedin.com/company/aiven/> <https://twitter.com/aiven_io> *Aiven Deutschland GmbH* Alexanderufer 3-7, 10117 Berlin Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen Amtsgericht Charlottenburg, HRB 209739 B
