igelado/mett
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Workflow: move from GitLab to Forgejo #1

Merged
igelado merged 2 commits from igelado/forgejo-ci into main 2026-10-19 00:43:49 +00:00
Conversation 1 Commits 2 Files changed 4 +75 -77
igelado commented 2026-10-18 19:20:09 +00:00
Owner
Copy link

Moves mett's development workflow from GitLab to Forgejo at git.gelado.org, keeping the same rules.

  • .forgejo/workflows/ci.yml (workflow ci) runs the checks from .gitlab-ci.yml on every push: the Markdown link check, cargo fmt --check, cargo clippy -D warnings and cargo test. It runs on runners labelled docker, and caches the cargo registry and target/.
  • AGENTS.md describes the same workflow with pull requests: feature branches, a clean Codex review before the PR, the required ci / docs and ci / rust checks, a reply to every review comment with its conversation resolved, and branch deletion on merge.
  • .gitlab-ci.yml is removed. So is .coderabbit.yaml, because CodeRabbit doesn't support Forgejo; the clean Codex review result is posted on each PR instead.

The main protection rule (no direct pushes, required checks) and delete-branch-after-merge are set in the repository settings.

🤖 Generated with Claude Code

Moves mett's development workflow from GitLab to Forgejo at git.gelado.org, keeping the same rules. - `.forgejo/workflows/ci.yml` (workflow `ci`) runs the checks from `.gitlab-ci.yml` on every push: the Markdown link check, `cargo fmt --check`, `cargo clippy -D warnings` and `cargo test`. It runs on runners labelled `docker`, and caches the cargo registry and `target/`. - `AGENTS.md` describes the same workflow with pull requests: feature branches, a clean Codex review before the PR, the required `ci / docs` and `ci / rust` checks, a reply to every review comment with its conversation resolved, and branch deletion on merge. - `.gitlab-ci.yml` is removed. So is `.coderabbit.yaml`, because CodeRabbit doesn't support Forgejo; the clean Codex review result is posted on each PR instead. The `main` protection rule (no direct pushes, required checks) and delete-branch-after-merge are set in the repository settings. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
CI: Forgejo Actions for the copy at git.gelado.org
All checks were successful
/ docs (push) Successful in 25s
Details
/ rust (push) Successful in 8m5s
Details
d6e028c87d 
Runs the docs and Rust checks of .gitlab-ci.yml on every push to the
Forgejo copy, with the cargo registry and target directory cached.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Workflow: move from GitLab to Forgejo at git.gelado.org
All checks were successful
ci / docs (push) Successful in 23s
Details
ci / rust (push) Successful in 2m26s
Details
cdac4f9846 
The repository now lives on Forgejo. AGENTS.md describes the same
workflow with pull requests: feature branches, a clean Codex review
before the PR, required CI checks, answered and resolved review
conversations, and branch deletion on merge.

Forgejo Actions is now the only CI, so .gitlab-ci.yml goes. CodeRabbit
doesn't support Forgejo, so .coderabbit.yaml goes too; the Codex review
result is posted on each PR instead.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
igelado commented 2026-10-18 19:20:15 +00:00
Author
Owner
Copy link

Codex review of cdac4f9 against main: clean.

The Forgejo workflow preserves the existing documentation and Rust checks, and the GitLab and CodeRabbit removals are consistent with the stated migration. I found no actionable regression in the diff.

The previous commit, d6e028c, was also reviewed clean.

**Codex review** of `cdac4f9` against `main`: clean. > The Forgejo workflow preserves the existing documentation and Rust checks, and the GitLab and CodeRabbit removals are consistent with the stated migration. I found no actionable regression in the diff. The previous commit, `d6e028c`, was also reviewed clean.
igelado deleted branch igelado/forgejo-ci 2026-10-19 00:43:49 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
igelado/mett!1
No description provided.