./blog/website-gitlab-migration

I’m moving my personal website repository to GitLab!

This is a small first step toward exploring GitLab as a development platform. Instead of migrating all my repositories at once, I’ve decided to start with my website and use it as an opportunity to learn the platform and test how it fits into my workflow.

Why GitLab?

GitHub has been an important part of my journey as a developer, and it will continue to be part of my development ecosystem. However, I’ve wanted to explore GitLab more seriously, and moving a relatively small project is a practical way to get started.

This gives me the opportunity to experiment with repository management, CI/CD, and the overall development workflow without committing to a full migration.

What happens to GitHub?

The GitHub repository will remain available as a mirror of the GitLab repository. GitLab will become the primary location for the website’s source code, while GitHub will continue to provide an additional way to access it.

For now, this change applies only to my personal website. My other repositories will remain where they are while I explore GitLab and decide whether migrating them would make sense.

One step at a time

This is an experiment, not a commitment to migrate everything. I’ll use this opportunity to become more familiar with GitLab and evaluate whether it deserves a larger role in my development workflow.

One repository at a time.

• If it hasn’t worked out yet, it’s because it’s not over yet