Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
fix(tools): fix and accelerate automated gitpod dev setup #36720
The fix was to switch freeCodeCamp to Gitpod's official MongoDB image.
I also noticed that initializing a freeCodeCamp workspace takes a long time, so I made efforts to optimize the setup, in order to save contributors and maintainers a lot of time:
The setup can probably be accelerated even further, but this is what I could reasonably achieve with my limited knowledge of the bootstrap process.
Then I've also added a new README badge, with a URL that can open any freeCodeCamp fork or branch in Gitpod:
(It's referrer-based, so if you click on it here, it will open my Pull Request in Gitpod.
Please let me know what you think.
Wow, thanks for merging my PR so fast!
Cool! I confirm that prebuilds are now enabled and working on the main freeCodeCamp repository. I hope this will make a lot of developers happy.
@raisedadead Good point. That link there currently points to:
which will always open the central repository in Gitpod, regardless of where it is clicked. If we change it to:
it will always open whichever repository CONTRIBUTING.md was consulted on. But maybe developers will always read CONTRIBUTING.md in the main freeCodeCamp repository, i.e. not in their fork?
TL;DR - I'm not sure which option is preferable for CONTRIBUTING.md specifically, but I don't think we need to change it now. If you have a preference, please let me know.
Thanks, yes.. this sure will help a lot of the contributors. We are looking forward for the feedback from the community.
Our only concern is sometimes our moderators (with write access to the repo) may accidentally push to the main repository. I am not sure if there is a clean way to handle that? We would always want everyone to push to their forks and not the upstream.
Ah, yes, that's a valid concern. I've trained myself to compulsively check
I see that the
Yes, while you are correct that GitHub allows for some protection. We do make fast forward merges to our release branches. Nonetheless, I am of the opinion that its not an issue that GitPod needs to solve.
I am pretty sure we can work with GitHub's settings to achieve what we need.