You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I sometimes have an itch to get involved again with this project. But then I think about how much work it is to get set up for development, and give up. 😞
A project I help with has a GitHub Codespaces configuration 1, with a Docker container and Codespaces specific config.
This all means I can click a button in the GitHub interface and get coding. 🥳 I don't have to worry about dependencies, as Codespaces will install the latest dependencies in the branch automatically. When I'm done working, I throw the container away, and start with a fresh one for the next change.
We'll definitely need help from somebody who knows their way around Docker and Codespaces 2. I don't know enough to get us started.
Rough todo list:
Make sure manual steps to build are complete and work
Figure out requirements to build book
Translate those requirements into a working Codespaces configuration
What problem will this solve?
We'll get more contributors by making it as easy as possible to get started. Right now, a contributor needs to figure out a lot of stuff to get started.
Have you thought about other solutions?
Keep things as they are, and keep relying on users setting up a local workstation with the manual instructions.
General overview of your idea.
I sometimes have an itch to get involved again with this project. But then I think about how much work it is to get set up for development, and give up. 😞
A project I help with has a GitHub Codespaces configuration 1, with a Docker container and Codespaces specific config.
This all means I can click a button in the GitHub interface and get coding. 🥳 I don't have to worry about dependencies, as Codespaces will install the latest dependencies in the branch automatically. When I'm done working, I throw the container away, and start with a fresh one for the next change.
We'll definitely need help from somebody who knows their way around Docker and Codespaces 2. I don't know enough to get us started.
Rough todo list:
What problem will this solve?
We'll get more contributors by making it as easy as possible to get started. Right now, a contributor needs to figure out a lot of stuff to get started.
Have you thought about other solutions?
Keep things as they are, and keep relying on users setting up a local workstation with the manual instructions.
Do you want to help with this enhancement idea?
Maybe
Footnotes
https://github.com/renovatebot/renovate/tree/main/.devcontainer ↩
https://docs.github.com/en/codespaces ↩
The text was updated successfully, but these errors were encountered: