test-actions

This repository preserves example Forgejo Actions workflows: a basic CI-style workflow and a static-site publishing workflow. It is reference material only: this Forgejo instance no longer has a runner or Git Pages hosting configured, so the workflows do not execute or deploy.

Actions explanation

This repo contains two Forgejo Actions workflows in .forgejo/workflows/:

• test.yaml

  • Runs on every push.
  • Prints context details (event, OS, repo) and verifies command execution on the runner.
  • Shows a simple smoke test for runner registration and workflow execution.

• pages.yaml

  • Runs on pushes to main.
  • Collects static content into _site/ (from public/ and/or index.html).
  • Shows how to publish _site/ using actions/git-pages@v2.

Static-site publishing reference

The publish workflow is retained as an example of the Git Pages URL pattern:

https://<user>.<PAGES_DOMAIN>/<repo>/

It builds that URL as:

https://${{ github.actor }}.${{ vars.PAGES }}/${{ github.event.repository.name }}/

Configuration needed to reuse it

1. In Forgejo, set repository or organization variable:
   • PAGES = your Git Pages domain (example: pages.example.com)
2. Ensure the workflow has access to:
   • forge.token for actions/git-pages@v2 authentication
3. Register a Forgejo runner, then push changes to the main branch to trigger deployment.

Site content behavior

During deployment, the workflow prepares _site/ like this:

• Copies everything from public/ if it exists.
• Copies root index.html if it exists.

So you can deploy by adding either:

• a public/ folder with static files, or
• a root index.html file.