You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2022/07/23 16:42:49 UTC

[GitHub] [airflow] Hasan-J commented on pull request #25251: Make codespace run successfully

Hasan-J commented on PR #25251:
URL: https://github.com/apache/airflow/pull/25251#issuecomment-1193153169

   I share the same disappointment with you indeed and I'm only on the beta too.
   
   Originally I wanted to avoid setting up my local machine, so I went the route of dockerizing everything, even my development environments to keep my sanity. Codespaces with their current "free" state are enough for specific types of contributions as you explained but what do you think about supporting Microsoft dev containers?
   
   First, I thought this would be impossible because you would need to combine Codespaces and dev-containers configurations
   but with the way codespace instance launching works we could separate them into `.devcontainer/.devcontainer-codespaces.json` & keep the `.devcontainer/devcontainer.json` for the local devcontainer workflow.
   
   This will allow power users to keep working the same way only without affecting their local machine binaries (only talking about external dependencies for the local virtual env setup here)
   
   Is it worth it?
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org