Could you add a devcontainer configuration to this repo? #6473
-
None of the issue types seem applicable, so this seems like the best place to ask. I like to use GitHub Codespaces, especially for large repos that might take up space locally, or require a lot of extra installed tools. The base codespace template is good enough to get started, but a custom
So, yeah, it's not necessary since the default config already comes with Ruby, but it helps skip past the "Dependencies" and "Getting Started" parts of the contributing doc and go straight to the actual contribution instructions. Edit: looks like there was a bit of work done here, but it doesn't seem like the PR author is going to continue soon. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
Definitely! I started this a while back when Codespaces was first launched before pre-builds were available as it would give everyone a consistent dev env but found it took waaaaay too long versus using the default container which is quick and does everything out the box so I've not looked at it since (eagle eyed viewers may have even spotted the branch hanging around for a while 😁). Now we've got pre-builds we should be able to speed this up considerably. I'll try carve out some time in the next few months (day job takes priority, and it's not linguist). If you've got the time and resources, feel free to make a start on it, and we can work on it together. |
Beta Was this translation helpful? Give feedback.
Definitely! I started this a while back when Codespaces was first launched before pre-builds were available as it would give everyone a consistent dev env but found it took waaaaay too long versus using the default container which is quick and does everything out the box so I've not looked at it since (eagle eyed viewers may have even spotted the branch hanging around for a while 😁). Now we've got pre-builds we should be able to speed this up considerably.
I'll try carve out some time in the next few months (day job takes priority, and it's not linguist). If you've got the time and resources, feel free to make a start on it, and we can work on it together.