Bookr Docs

Appearance

Gitea Actions Configuration Notes ​

Key Differences from GitHub Actions ​

Variables ​

- `${{ github.* }}` → `${{ gitea.* }}`
- `$GITHUB_OUTPUT` → `$GITEA_OUTPUT`
- `${{ github.event.inputs.* }}` → `${{ inputs.* }}`

Workflow Features ​

  • Workflow reuse: Limited support, inlined checks instead of uses: ./.gitea/workflows/check.yaml
  • Complex expressions: Simplified run-name expressions for better compatibility
  • Matrix strategies: Same syntax as GitHub Actions
  • Secrets: Same syntax as GitHub Actions

Environment Variables ​

Updated the following in workflows:

  • gitea.ref_name - Current branch name
  • gitea.event_name - Event type (push, workflow_dispatch, etc.)
  • gitea.sha - Commit SHA
  • $GITEA_OUTPUT - For setting step outputs

Actions Used ​

All actions used are compatible with Gitea Actions:

  • actions/checkout@v4
  • pnpm/action-setup@v3
  • actions/setup-node@v3
  • docker/setup-buildx-action@v3
  • docker/login-action@v3

Configuration Changes Made ​

  1. deploy.yaml: Updated all GitHub variables to Gitea equivalents
  2. check.yaml: Updated github.ref_name to gitea.ref_name
  3. Workflow reuse: Inlined checks job instead of using workflow reuse
  4. Output variables: Changed $GITHUB_OUTPUT to $GITEA_OUTPUT
  5. Input references: Changed github.event.inputs.* to inputs.*

Testing Recommendations ​

  1. Test on a feature branch first to verify workflow syntax
  2. Check Actions logs for any Gitea-specific error messages
  3. Verify secrets are accessible in Gitea repository settings
  4. Monitor workflow runs to ensure proper execution

Gitea Actions Documentation ​

For the latest Gitea Actions syntax and features, refer to:

Known Limitations ​

  1. Workflow reuse may have limited support compared to GitHub Actions
  2. Complex expressions in run-name may need simplification
  3. Some GitHub Actions may not be fully compatible with Gitea Actions

If you encounter issues, consider:

  • Simplifying workflow expressions
  • Using environment variables instead of complex conditionals
  • Testing individual steps locally with act or similar tools