basepeak-ai/go-gptscript
Watch
6
0
Fork
You've already forked go-gptscript
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

ci: test on Forgejo with our gptscript release #4

Merged
thklein merged 2 commits from ci/forgejo-only into main 2026-10-17 21:25:28 +00:00
Conversation 0 Commits 2 Files changed 6 +38 -124
thklein commented 2026-10-17 20:57:53 +00:00
Owner
Copy link

CI now runs on Forgejo and uses our gptscript release.

  • Removed the GitHub repository_dispatch tag and release workflow.
  • Removed the reusable-workflow setup:
    • Forgejo rejects workflow_call.secrets.
    • The permission check calls the GitHub API.
  • One test.yaml:
    • Runs make validate.
    • With provider keys, also fetches gptscript v0.9.10 from our private Forgejo release (org read token, curl with a 5-minute cap) instead of get.gptscript.ai, and runs make test. The org currently has no provider keys.
  • Makefile: the golangci-lint install script is pinned to the linter version instead of master (master's script has shipped bad checksums before).

make validate passes locally (0 issues, clean tree).

CI now runs on Forgejo and uses our gptscript release. - Removed the GitHub `repository_dispatch` tag and release workflow. - Removed the reusable-workflow setup: - Forgejo rejects `workflow_call.secrets`. - The permission check calls the GitHub API. - One `test.yaml`: - Runs `make validate`. - With provider keys, also fetches gptscript `v0.9.10` from our private Forgejo release (org read token, curl with a 5-minute cap) instead of `get.gptscript.ai`, and runs `make test`. The org currently has no provider keys. - `Makefile`: the golangci-lint install script is pinned to the linter version instead of `master` (master's script has shipped bad checksums before). `make validate` passes locally (0 issues, clean tree).
ci: test on Forgejo with our gptscript release
Some checks failed
pull_request.yaml / ci: test on Forgejo with our gptscript release (pull_request_target) Failing after 0s
Details
test / test (pull_request) Has started running
Details
20bfc0f025
 
Drop the GitHub repository_dispatch release and the reusable-workflow
setup (Forgejo rejects workflow_call secrets; the permission check
calls the GitHub API). One workflow runs make validate, and with
provider keys fetches gptscript from our private Forgejo release
instead of get.gptscript.ai. The golangci-lint install script is
pinned to the linter version instead of master.
ci: re-run after runner MTU fix
Some checks failed
pull_request.yaml / ci: re-run after runner MTU fix (pull_request_target) Failing after 0s
Details
test / test (pull_request) Successful in 24s
Details
6dbaf01a2f
thklein deleted branch ci/forgejo-only 2026-10-17 21:25:28 +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
basepeak-ai/go-gptscript!4
No description provided.