GameCult/Ratatoskr
Watch
9
0
Fork
You've already forked Ratatoskr
 0
Code Issues Pull requests 2 Projects Releases Packages Wiki Activity Actions 1

ci: drop Cinny-upstream workflows that cannot run on the forge #25

Merged
void merged 1 commit from void/ci-drop-cinny-leftovers into main 2026-11-07 11:39:22 +00:00
Conversation 0 Commits 1 Files changed 6 -251
void commented 2026-11-07 11:38:37 +00:00
Member
Copy link

Workflows only. No app code touched. Removes the Cinny-upstream workflows that cannot work on our forge; chat.gamecult.org deploys go through Idunn, not these.

Removed, and why each is dead

  • cla.yml: Cinny's CLA bot. It runs cla-assistant/github-action, which the forge runner resolves against data.forgejo.org and cannot find (remote: Not found, run 107 on #17). It also needs cinnyapp/cla and a CLA_PAT secret, and it fires on every PR and every issue comment.
  • pr-title.yml: amannn/action-semantic-pull-request, a GitHub-API check on Cinny's conventional-title policy. We do not follow that policy (titles like "sky: ..." and "auth: ..." are our own), and it runs on pull_request_target.
  • deploy-pull-request.yml: a workflow_run that posts a Netlify preview using NETLIFY_AUTH_TOKEN_PR and NETLIFY_SITE_ID_PR_CINNY. We have neither and do not deploy to Netlify.
  • netlify-dev.yml: pushes dev to Netlify with NETLIFY_AUTH_TOKEN and NETLIFY_SITE_ID_DEV. We have no such secrets and no dev branch in use.
  • prod-deploy.yml: on release, deploys to Netlify (NETLIFY_SITE_ID_APP), GPG-signs a tarball (GNUPG_KEY, GNUPG_PASSPHRASE), and pushes cinny images to Docker Hub (DOCKER_USERNAME, DOCKER_PASSWORD) and GHCR. We hold none of those secrets and do not publish this way.

Kept

  • build-pull-request.yml (ubuntu-latest, npm ci and a Vite build). It runs on the forge today.
  • lockfile.yml (ubuntu-latest, no secrets beyond the built-in token). It comments on lockfile diffs through a GitHub-API action that I have not verified against the forge. It only triggers on package-lock.json changes.
  • docker-pr.yml (ubuntu-latest, builds the Dockerfile with push off; the registry logins are continue-on-error). It only triggers on Dockerfile changes. One line changed: the deleted prod-deploy.yml path is dropped from its trigger filter.

Nothing in the kept workflows asks for a Windows or macOS label.

🤖 Generated with Claude Code

Workflows only. No app code touched. Removes the Cinny-upstream workflows that cannot work on our forge; chat.gamecult.org deploys go through Idunn, not these. **Removed, and why each is dead** - `cla.yml`: Cinny's CLA bot. It runs `cla-assistant/github-action`, which the forge runner resolves against `data.forgejo.org` and cannot find (`remote: Not found`, run 107 on #17). It also needs `cinnyapp/cla` and a `CLA_PAT` secret, and it fires on every PR and every issue comment. - `pr-title.yml`: `amannn/action-semantic-pull-request`, a GitHub-API check on Cinny's conventional-title policy. We do not follow that policy (titles like "sky: ..." and "auth: ..." are our own), and it runs on `pull_request_target`. - `deploy-pull-request.yml`: a `workflow_run` that posts a Netlify preview using `NETLIFY_AUTH_TOKEN_PR` and `NETLIFY_SITE_ID_PR_CINNY`. We have neither and do not deploy to Netlify. - `netlify-dev.yml`: pushes `dev` to Netlify with `NETLIFY_AUTH_TOKEN` and `NETLIFY_SITE_ID_DEV`. We have no such secrets and no `dev` branch in use. - `prod-deploy.yml`: on release, deploys to Netlify (`NETLIFY_SITE_ID_APP`), GPG-signs a tarball (`GNUPG_KEY`, `GNUPG_PASSPHRASE`), and pushes `cinny` images to Docker Hub (`DOCKER_USERNAME`, `DOCKER_PASSWORD`) and GHCR. We hold none of those secrets and do not publish this way. **Kept** - `build-pull-request.yml` (`ubuntu-latest`, `npm ci` and a Vite build). It runs on the forge today. - `lockfile.yml` (`ubuntu-latest`, no secrets beyond the built-in token). It comments on lockfile diffs through a GitHub-API action that I have not verified against the forge. It only triggers on `package-lock.json` changes. - `docker-pr.yml` (`ubuntu-latest`, builds the Dockerfile with push off; the registry logins are `continue-on-error`). It only triggers on Dockerfile changes. One line changed: the deleted `prod-deploy.yml` path is dropped from its trigger filter. Nothing in the kept workflows asks for a Windows or macOS label. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
ci: drop Cinny-upstream workflows that cannot run on the forge
Some checks failed
CLA Assistant / CLAssistant (pull_request_target) Failing after 1s
Details
Check PR title / lint (pull_request_target) Failing after 1s
Details
Build pull request / Build pull request (pull_request) Failing after 3m37s
Details
Docker check / docker-build (pull_request) Failing after 15s
Details
d670fc5391 
Remove cla, pr-title, deploy-pull-request, netlify-dev and prod-deploy;
drop the deleted prod-deploy path from docker-pr's trigger filter.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
void merged commit aa2eef089d into main 2026-11-07 11:39:22 +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
GameCult/Ratatoskr!25
No description provided.