ci(forgejo): port main automation workflows #345

Merged
barrettruth merged 1 commit from ci/forgejo-automation-workflows into main 2026-05-02 02:02:30 +00:00
Owner

Summary

  • add Forgejo-native issue/PR automation workflows for main
  • port upstream digest to scripts/upstream_digest.py without the GitHub CLI
  • add Forgejo API helper for pushing/opening upstream digest PRs
  • schedule both main and canola upstream digests from the default branch, because Forgejo ignores scheduled workflows on non-default branches
  • add required curl, git, jq, and python3 tools to the dev shell

Branch note

This PR targets main. It schedules the default-branch digest and also checks out canola to run the scheduled canola digest. The canola branch still has its own separate manual workflow PR because the two branches are not the same branch and need branch-specific settings.

Verification

  • workflow YAML parsed with yq
  • shell scripts passed shfmt, shellcheck, and bash -n
  • python3 -m py_compile scripts/upstream_digest.py
  • nix develop .#ci --command just format
  • nix develop .#ci --command just lint
  • upstream digest dry-run fetched upstream activity and reported pending additions
  • upstream digest PR helper dry-run refused to push/open a PR
  • live smoke: temporary issue #342 had question removed and was closed
  • live smoke: requested Barrett review on draft PR #195, verified reviewer appeared, then canceled back to empty

Known test issue

Local just test currently fails on baseline origin/main too: spec/altbuf_spec.lua @ 56 times out waiting for User. This appears pre-existing/local-environment-sensitive, not caused by this workflow port, but it must be fixed in follow-up and is recorded in nix AGENTS.md.

## Summary - add Forgejo-native issue/PR automation workflows for `main` - port upstream digest to `scripts/upstream_digest.py` without the GitHub CLI - add Forgejo API helper for pushing/opening upstream digest PRs - schedule both `main` and `canola` upstream digests from the default branch, because Forgejo ignores scheduled workflows on non-default branches - add required `curl`, `git`, `jq`, and `python3` tools to the dev shell ## Branch note This PR targets `main`. It schedules the default-branch digest and also checks out `canola` to run the scheduled canola digest. The `canola` branch still has its own separate manual workflow PR because the two branches are not the same branch and need branch-specific settings. ## Verification - workflow YAML parsed with `yq` - shell scripts passed `shfmt`, `shellcheck`, and `bash -n` - `python3 -m py_compile scripts/upstream_digest.py` - `nix develop .#ci --command just format` - `nix develop .#ci --command just lint` - upstream digest dry-run fetched upstream activity and reported pending additions - upstream digest PR helper dry-run refused to push/open a PR - live smoke: temporary issue #342 had `question` removed and was closed - live smoke: requested Barrett review on draft PR #195, verified reviewer appeared, then canceled back to empty ## Known test issue Local `just test` currently fails on baseline `origin/main` too: `spec/altbuf_spec.lua @ 56` times out waiting for `User`. This appears pre-existing/local-environment-sensitive, not caused by this workflow port, but it must be fixed in follow-up and is recorded in nix `AGENTS.md`.
ci(forgejo): port automation workflows
All checks were successful
quality / Lint (pull_request) Successful in 9s
quality / Format (pull_request) Successful in 14s
quality / Test (pull_request) Successful in 10s
a13bb61713
barrettruth force-pushed ci/forgejo-automation-workflows from a13bb61713
All checks were successful
quality / Lint (pull_request) Successful in 9s
quality / Format (pull_request) Successful in 14s
quality / Test (pull_request) Successful in 10s
to 4dc0b2bf82
All checks were successful
quality / Lint (pull_request) Successful in 6s
quality / Test (pull_request) Successful in 7s
quality / Format (pull_request) Successful in 8s
2026-05-02 01:58:40 +00:00
Compare
barrettruth deleted branch ci/forgejo-automation-workflows 2026-05-02 02:02:30 +00:00
Sign in to join this conversation.
No description provided.