#283 [Feature] CodeCoverage Gate for Various components Issue created by kumare3 Motivation: Why do you think this is important? Recently I have noticed that code coverage has dropped for some of our components. We should ensure that code coverage keeps improving or atleast stays the same. Goal: What should the final outcome look like, ideally? In case a PR drops code coverage, it should not be allowed to checkin Describe alternatives you've considered Code reviews, but that is not enforceable Flyte component ☐ Overall ☐ Flyte Setup and Installation scripts ☐ Flyte Documentation ☐ Flyte communication (slack/email etc) ☑︎ FlytePropeller ☐ FlyteIDL (Flyte specification language) ☑︎ Flytekit (Python SDK) ☑︎ FlyteAdmin (Control Plane service) ☑︎ FlytePlugins ☑︎ DataCatalog ☑︎ FlyteStdlib (common libraries) ☑︎ FlyteConsole (UI) ☐ Other [Optional] Propose: Link/Inline NA Additional context NA Is this a blocker for you to adopt Flyte No, but as a contributor my confidence will improve to checkin new code. flyteorg/flyte