GitLab alternative
If you use GitLab for repositories, issues and code review, and do not want to maintain a server, Skillok covers that part. If you live in GitLab CI and the package registry — honestly, that is not us yet. Here is what matches and what does not.
In this article
What matches everyday work in GitLab#
- Git repositories, public and private, HTTPS access with a token, Git LFS.
- Branches with protection and a
CODEOWNERSfile — who is responsible for which parts of the code. - Issues with labels, milestones, assignees and attachments.
- Pull requests (merge requests in GitLab) with review: approve or request changes, request reviewers.
- Projects with a table, a board and a roadmap — the counterpart of issue boards.
- Organizations and teams with access roles for repositories: read, triage, write, maintain. An organization audit log.
- Webhooks on repository events, signed with HMAC-SHA256 — you can hook your own build to them.
What is missing#
- Built-in CI/CD. There are no pipelines, runners, or package and container registries. A build can be started by an external system on a webhook.
- Import of GitLab projects — code moves with git commands, issues by hand.
- Self-hosting on your own server. Skillok runs as a service.
- Squash and rebase on merge, code search, wikis.
Limits: up to 25 repositories per owner, up to 2 GB per repository.
How to move your code#
Create the empty repository beforehand; pushing needs a personal token from
your settings. All branches and tags come along; LFS files go with a separate
git lfs push --all.
Who it suits#
A team of a few people who need a clear cycle "issue → branch → review → merge" and a project board, but no build infrastructure of their own. If CI is the heart of your work, stay on GitLab or connect an external build through webhooks. For a side-by-side with the other familiar host, see the GitHub alternative page.
Try it on your own task
Create a repository — history, issues and pull requests from day one.
Was this helpful?