How to Use Gitpod (now Ona)

Getting started with Gitpod

In this guide, you'll learn how to set up and use Gitpod to create cloud-based development environments directly from your Git repository. After reading, you'll be ready to start coding without the usual setup hassle.

Step 1: Sign up and set up

1. Go to Gitpod's website.
2. Click on the Sign Up button in the top right corner.
3. You can sign up using your GitHub, GitLab, or Bitbucket account. Click the relevant option and authorise Gitpod to access your repositories.
4. Once signed up, you’ll be taken to your Gitpod dashboard. Here, you can see your workspace history and manage your settings.

Step 2: Your first workspace

1. Navigate to a Git repository you want to work on (e.g., on GitHub).
2. In the repository, add gitpod.io# before the URL in your browser's address bar (e.g., change https://github.com/username/repo to https://gitpod.io#https://github.com/username/repo) and hit Enter.
3. Gitpod will start a new workspace. This may take a moment as it sets up the environment.
4. Once the workspace is ready, you’ll see a cloud-based IDE with a terminal, file explorer, and editor. You can start coding directly.

Step 3: Get better results

1. Use the .gitpod.yml file in your repository to configure your workspace. This file allows you to define tasks, prebuilds, and settings that automatically run when your workspace starts.
2. Take advantage of the terminal to install any dependencies required for your project. Use commands like npm install or pip install as needed.
3. Explore the Extensions panel (left sidebar) to install additional tools or plugins that can enhance your coding experience.

Pro tip

Set up a prebuild in your .gitpod.yml file to automatically install dependencies and run setup scripts when a workspace is created. This saves time and ensures every workspace is ready to go without manual setup.

Common mistake to avoid

Avoid using Gitpod without checking the prebuilt configuration. If you don’t define a .gitpod.yml file, you might end up spending time installing dependencies manually in each new workspace, defeating the purpose of automation.