I’m starting to move some open source stuff of mine over to Codeberg, and since a big part of that is Typst packages, I have adapted the community’s package template to more easily support that—and I’ve composed a blog post about the result: Developing Typst Packages on Codeberg
Here’s a small excerpt from the workflow changes:
--- a/.github/workflows/tests.yml
+++ b/.github/workflows/tests.yml
@@ -24,27 +24,29 @@ jobs:
doc: true
name: Test for ${{ matrix.typst-version.typst }} (Tytanic ${{ matrix.typst-version.tytanic }}${{ matrix.typst-version.doc && ', with docs' }})
- runs-on: ubuntu-latest
+ runs-on: codeberg-tiny
steps:
- name: Checkout
uses: actions/checkout@v6
- name: Setup typst
id: setup-typst
- uses: typst-community/setup-typst@v4
+ uses: https://github.com/typst-community/setup-typst@v4
with:
typst-version: ${{ matrix.typst-version.typst }}
+ token: ${{ secrets.BASIC_GITHUB_TOKEN }}
@@ -53,7 +55,7 @@ jobs:
run: just test
- name: Archive test results
- uses: actions/upload-artifact@v4
+ uses: forgejo/upload-artifact@v4
if: always()
with:
name: typst-${{ steps.setup-typst.outputs.typst-version }}-test-results
It was a fairly smooth experience, and it turns out Codeberg even makes some parts of package setups simpler than Github, because it supports user-wide CI secrets!