Opening workspaces based on repositories without commit rights—like the example above—is useful for exploring. However, when using gitpod day-to-day, you would typically use a repo you own (or have forked).
Fork the EventHub repository
Let’s fork the EventHub repository to continue. Go to the repository on GitHub and click “Fork”. This will create a copy of the code in your own Organization.Open your repository
With your repository now forked, let’s initialise a new workspace with editable code by prefixing your git URL withhttps://gitpod.io/# — for example:
Explore the workspace
With your workspace up, why not take a look around. Try the following:- Open/edit a file - See how Gitpod has pulled all your files for you.
- Explore default tools - By running
npm -vorpython --version. - Check workspace specs - Run
gp topfor workspace memory and CPU.
Anything you can do in Linux you can do in Gitpod. Go ahead—play around !