Creating a workflow for testing the ruby feature. I use the devcontainer/ci step to create a devcontainer using the ruby feature and check that ruby is installed. I think that's sufficient for now.
I am pushing the test image to ghcr.io/rails/devcontainer/test-ruby-feature so it can be cached. Without a cache this workflow takes about ~10 minutes, about 6 of that is actually installing ruby, so the cache is quite helpful. I set this up to only push the image if it is from main. We should make that package private probably.
I created a link to the features directory in the .github/.devcontainer directory (where the devcontainer used in the test lives). That way the local version of the feature can be used by the devcontainer. I tried to do this by mounting that folder in the devcontainer but it didn't seem to work 🤔 , so I went with the link instead.
Creating a workflow for testing the ruby feature. I use the
devcontainer/cistep to create a devcontainer using the ruby feature and check that ruby is installed. I think that's sufficient for now.I am pushing the test image to
ghcr.io/rails/devcontainer/test-ruby-featureso it can be cached. Without a cache this workflow takes about ~10 minutes, about 6 of that is actually installing ruby, so the cache is quite helpful. I set this up to only push the image if it is frommain. We should make that package private probably.I created a link to the
featuresdirectory in the.github/.devcontainerdirectory (where the devcontainer used in the test lives). That way the local version of the feature can be used by the devcontainer. I tried to do this by mounting that folder in the devcontainer but it didn't seem to work 🤔 , so I went with the link instead.