> > If you feel this is worth a shot, I will try to contribute gitpod support. > (It involves a .gitpod.yml and which has tasks definition for setup commands > and open ports). >
Absolutely. I'd love to review and try it after you make PR. > I think the barrier also applies to airflow website - it has complex commit > hooks, ssh for submodules, etc. It could be an easier starting point for GitPod as there are quite a bit less "moving parts" in airflow-site, but big part of it (submodules and most pre-commits for one) are pretty much the same as in the main airflow repo. J
