-
-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🛠️ Neighborhood
: Contributors
can use DevContainers
and Codespaces
#1433
Comments
Current WorkaroundWhen my CodeSpace was in this state, I was able to run Why it wouldn't do this correctly upon the first starup/attach, I don't know... |
Neighborhood
: Contributor DevContainer
and Codespaces
Neighborhood
: Contributor DevContainer
and Codespaces
Neighborhood
: Contributors
can use DevContainers
and Codespaces
Forked repos cannot use the devcontainer due to it being private to the organization. Should be able to fix by making it either public or somehow linked to forked repos. Needs further investigation and/or testing. |
@daltonrpruitt - Nice catch! I've made it public. |
Darn I keep encountering a variation of this issue where permission is denied to a specific file. Thanks @daltonrpruitt for the workaround to get me unstuck. I just spun up a fresh code space instance on my feature branch #1602 and hit this error loading the front end. |
Hmm. I am annoyed the fresh CodeSpace instances aren't working suddenly for some reason. I will have to look into this later. Thank you for the info! |
Thanks so much for all your hard work on improving the code spaces @daltonrpruitt! ❤️ It's been a huge help when my local dev enviro gets messed up. It feels great knowing I can use code spaces as my primary or back up dev enviro/coding space. |
Glad you were able to find a workaround; bummer that our current codespaces are a touch brittle but I'm glad we're using them and learning how to debrittle them!!! |
Neighborhoods
#892Convene's DevContainer streamlines the contributor experience by:
Known Issues
Could not open directory "pg_logical/snapshots": Permission denied
Current Workaround
The text was updated successfully, but these errors were encountered: