Support Codeberg and GitLab for Code Repositories

[egrace479]

I did a review of the repository attributes we used for Codeberg and GitLab:

GitHub (Attribute)	Codeberg	GitLab
name	✅	✅
full_name	✅	name_with_namespace
fork	✅	❌ (No clear indicator)
forks_count	✅	✅
created_at	✅	✅
updated_at	✅	✅
topics	✅	✅
archived	✅	✅
description	✅	✅
html_url	✅	web_url
stargazers_count	stars_count	star_count

Codeberg repo attributes and GitLab project attributes.

We can then do stars: repo.stargazers_count || repo.stars_count || repo.star_count and similar in other locations where the attributes differ. It looks like we could potentially check forked_from_project for GitLab (I think it would be existence of this key indicating it's a fork).

Key distinctions in API calls:

Request	GitHub	Codeberg	GitLab
List all repos in Org	https://api.github.com/orgs/${ORGANIZATION_NAME}/repos?type=public&per_page=100	https://codeberg.org/api/v1/orgs/${ORGANIZATION_NAME}/repos?limit=50	https://gitlab.com/api/v4/groups/${ORGANIZATION_NAME}/projects?visibility=public&per_page=100
get repo info	https://api.github.com/repos/${ownerRepo}	https://codeberg.org/api/v1/repos/${ownerRepo}	https://gitlab.com/api/v4/projects/${ownerRepo}
Org	orgs/	orgs/	groups/
visibility	type=public	default is public without authentication, may support type=public	visibility=public
pagination	per_page=100	limit=50	per_page, limit needs to be checked
Request (URL end)	/repos?type=public&per_page=100	/repos?limit=50	/projects?visibility=public&per_page=100
Repo	repos/	repos/	projects/1

Discussed with @thompsonmj, and it seems simplest for an end-user to have a single PLATFORM key in the config file, then define the URLs based on the designated platform ('github', 'codeberg', or 'gitlab'). We'd set 'github' as the default. The URL definitions are needed in main.js and the two scripts (export-tags.js and fetch-releases.js, which would need some other platform-specific modifications). Then index.html needs the platform for the Ribbon: title and SVG vector path definition. This would also avoid concerns about trailing slashes because we will be constructing URLs.

Footnotes

1. For GitLab, it emphasizes URL-encoded NAMESPACE/PROJECT_PATH or the project id can be used (this is relevant for the ADDITIONAL_REPOS config; regular repo info fetch uses full_name). ↩

[egrace479]

Codeberg

Codeberg latest release call is ${REPO_API_URL}${ORGANIZATION_NAME}/${CATALOG_REPO_NAME}/releases/latest, which includes a tag_name property, so it matches GitHub (existing functionality).

Example call and response

Call

curl -X 'GET' \
  'https://codeberg.org/api/v1/repos/erffy/zig-waybar-contrib/releases/latest' \
  -H 'accept: application/json'

Response

{
  "id": 9180228,
  "tag_name": "26.05.08",
  "target_commitish": "",
  "name": "26.05.08",
  "body": "### Changes since 26.04.23\n- fix aur publishing (8b66f46)\n- pkgbuild: empty sum (f5942ed)\n- why this shit is not working? (f75a64a)\n- fix(aur): fix fix fix (9d7a32a)\n- fix(aur): another fix (4defc04)\n- fix(aur): another fix (c4061b8)\n- fix(aur): apply fix (493064b)\n- actions(aur): apply fix (84b3e1e)\n- refactor(aur): apply bug fixes (161855d)\n",
  "url": "https://codeberg.org/api/v1/repos/erffy/zig-waybar-contrib/releases/9180228",
  "html_url": "https://codeberg.org/erffy/zig-waybar-contrib/releases/tag/26.05.08",
  "tarball_url": "https://codeberg.org/erffy/zig-waybar-contrib/archive/26.05.08.tar.gz",
  "zipball_url": "https://codeberg.org/erffy/zig-waybar-contrib/archive/26.05.08.zip",
  "hide_archive_links": false,
  "upload_url": "https://codeberg.org/api/v1/repos/erffy/zig-waybar-contrib/releases/9180228/assets",
  "draft": false,
  "prerelease": false,
  "created_at": "2026-05-08T19:43:20+02:00",
  "published_at": "2026-05-08T19:43:20+02:00",
  "author": {
    "id": 686058,
    ...
    "username": "erffy"
  },
  "assets": [
    ...
  ],
  "archive_download_count": {
    "zip": 1,
    "tar_gz": 0
  }
}

Remaining question on Codeberg is the token use for release fetching.

GitLab

GitLab latest release is fetched with GET /projects/:id/releases/permalink/latest; it does include the tag_name property.

However, the response has released_at instead of published_at and web_url seems to be repo root instead of the release link keyed with html_url by GitHub and Codeberg (these are relevant for scripts/fetch-releases.js). We could perhaps construct the release URL.

GitLab example

It looks like the GitLab call should return at least the following (pulled out of the example return from their list releases call:

{
      "tag_name":"v0.2",
      "description":"## CHANGELOG\r\n\r\n- Escape label and milestone titles to prevent XSS in GLFM autocomplete. !2740\r\n- Prevent private snippets from being embeddable.\r\n- Add subresources removal to member destroy service.",
      "name":"Awesome app v0.2 beta",
      "created_at":"2019-01-03T01:56:19.539Z",
      "released_at":"2019-01-03T01:56:19.539Z",
      "author":{
         "id":1,
         "name":"Administrator",
         "username":"root",
         "state":"active",
         "avatar_url":"https://www.gravatar.com/avatar/e64c7d89f26bd1972efa854d13d7dd61?s=80\u0026d=identicon",
         "web_url":"https://gitlab.example.com/root"
},

I'm also currently unsure how the token will work for GitLab in fetch-releases.

[egrace479]

Regarding API org/repo calls. It looks like both GitHub and Codeberg APIs not case-sensitive, though GitLab org and repo names are case-sensitive (like HF, whose organization names are case-sensitive, though repos don't seem to be).

Seems it might make sense to update to fetching the catalog version from the package.json, also avoids an extra API call. Alternatively, this URL could be added to getPlatformApiUrls.

scripts/fetch-releases.js calls getPlatformApiUrls already (used in the release URL call: ${REPO_API_URL}${id}/releases/latest), and we can add a release_suffix key, which will be releases/latest for Codeberg and GitHub, and releases/permalink/latest for GitLab.

Both scripts also have .fork, .full_name, and the org profile repo name. It might make more sense to move the platform key lookup out of src/api/fetchCodeRepos.js since these keys are needed in multiple locations.