Skip to content

chore: move CI workflows from .github to .forgejo#114

Open
garrappachc wants to merge 3 commits into
masterfrom
chore/migrate-workflows-to-forgejo
Open

chore: move CI workflows from .github to .forgejo#114
garrappachc wants to merge 3 commits into
masterfrom
chore/migrate-workflows-to-forgejo

Conversation

@garrappachc
Copy link
Copy Markdown
Member

Summary

  • Moves all four workflow files (auto-release.yml, build.yml, publish.yml, release.yml) from .github/workflows/ to .forgejo/workflows/
  • Removes the now-empty .github/ directory
  • No workflow logic changed — this is a pure rename

Forgejo resolves workflows from .forgejo/workflows/ first; .github/workflows/ is only a GitHub-compatibility fallback and is not idiomatic for a Codeberg-native repo.

Test plan

  • Verify Forgejo picks up the workflows from the new path after merge
  • Confirm no workflow runs are broken (build, release, publish, auto-release)

🤖 Generated with Claude Code

garrappachc and others added 3 commits May 23, 2026 20:57
- Switch release-it from GitHub to Gitea releases (codeberg.org host)
- Replace GITHUB_TOKEN with GITEA_TOKEN for release-it authentication
- Remove npm OIDC provenance (not supported on Forgejo); use granular NPM_TOKEN instead
- Update git noreply email and Renovate bot email to Codeberg format

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Forgejo's idiomatic workflow directory is .forgejo/workflows/.
The .github/workflows/ path is only a compatibility fallback.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@sonarqubecloud
Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant