11 Commits

Include renames

Author	SHA1	Message	Date
rock	0c6abc3fef	ci: restore simple workflow - rust runner now has Node.js ... Updated in homelab: forgejo-runner-rust now uses docker:27-cli image which includes Node.js + git + docker + full dev tools. This allows actions/checkout@v4 and other GitHub Actions to work. Workflow simplified: - No container override (use runner's native environment) - Uses actions/checkout@v4 (requires Node.js) - Builds and pushes to registry Test commit to verify new runner configuration works.	2026-09-05 22:50:50 -07:00
rock	b40cc47729	ci: use rust runner native environment (no container override) ... The rust runner pod is pre-configured with: - Rust 1.83-bookworm base image - Docker CLI + Node.js (for GitHub Actions) - Git + all build tools - TLS-secured docker daemon connection at tcp://localhost:2376 Don't override with a container image. Use the runner's native environment. This is the correct pattern for self-hosted runners.	2026-09-05 22:46:43 -07:00
rock	31f5265603	ci: fix workflow - clone into /src directory ... Previous issue: git repo check at /workspace/rock failed Solution: - Clone repo explicitly into /src directory - cd /src for all git operations - Build from /src - Use github.sha environment variable for explicit checkout	2026-09-05 22:42:25 -07:00
rock	5cfff3990a	ci: simplify workflow - use current directory (repo auto-checked-out) ... Previous failure: git clone tried to clone into /workspace which already exists Fix: - Remove git clone step - Forgejo automatically checks out repo into current directory - Just install git, get commit info, build, and push - Much simpler and cleaner	2026-09-05 22:41:32 -07:00
rock	9807e7ec97	ci: fix workflow - use docker:27-dind container with git built-in ... Previous run failed because: - rust:1.83-bookworm container lacks Node.js (needed for actions/checkout) - Docker not available in the rust container - actions/checkout@v4 is a third-party action that needs Node Solution: - Use docker:27-dind container (has docker + git preinstalled) - Replace actions/checkout with direct git clone + checkout - All steps run directly in the docker container This matches Forgejo's native environment better than trying to run GitHub Actions inside a Rust container.	2026-09-05 22:40:27 -07:00
rock	9062c51545	ci: add workflow to .gitea/ (Gitea 1.27 expected path)	2026-09-05 22:38:52 -07:00
rock	6b03dea5d3	ci: remove old .gitea workflows - use .forgejo only ... The .gitea/ workflows were outdated and caused conflicts: - Used runs-on: rust, golang (non-existent runners) - Complex docker:27-cli setup with TLS (fragile) - Different secret variable names (FORGEJO_REGISTRY_TOKEN vs REGISTRY_PAT) - No tests before build .forgejo/workflows/build.yaml is the clean, working version: - Simplified docker commands - Proper runner: docker - Tests run first - Cleanup on failure - No hanging processes	2026-09-05 14:21:54 -07:00
rock	717ec65858	fix: restore .gitea/workflows (Gitea 1.27 reads .gitea/ not .forgejo/)	2026-08-28 15:53:02 -07:00
rock	6495b2213c	fix: remove duplicate .gitea/workflows (Forgejo reads .forgejo/)	2026-08-28 15:51:41 -07:00
Story Crater Bot	9f6502aec4	fix(ci): use git clone instead of actions/checkout (no node in rust image)	2026-08-23 17:35:45 -07:00
Story Crater Bot	4a10c53e18	fix(ci): move workflow to .gitea/workflows/ (Gitea ignores .forgejo/)	2026-08-23 17:34:44 -07:00