Skip to content

Fix problems with GitPod environments for forks with custom names

K M requested to merge crossner90/gitlab-fork:crossner90-master-patch-27066 into master

What does this MR do and why?

Today at KubeCon, while solving GitLab's code challenge I stumbled upon an issue with a fresh GitPod environment - none of my changes were visible in the running application. I took some time to debug it and the issue turned out to be related to the name of my fork (gitlab-fork). GitPod clones the repo into a directory following the pattern like /workspace/<repo-name> whereas one of the steps in .gitpod.yml naively assumes that the workspace path is always /workspace/gitlab.

Screenshots or screen recordings

These are strongly recommended to assist reviewers and reduce the time to merge your change.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

  1. Create a new GitPod workspace and try to edit any of the files (make sure your GitLab fork is not named gitlab).

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by K M

Merge request reports