behackl/pi-unigpt
Watch
1
0
Fork
You've already forked pi-unigpt
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

CI: move workflow to .github and use a subpath-aware checkout
Some checks failed
CI / test (22) (push) Failing after 0s
Details
CI / test (24) (push) Failing after 0s
Details

Browse source 
actions/checkout drops the /git subpath of our Gitea when building the
clone URL. Use ischanx/checkout v6.0.2, pinned to its commit.
This commit is contained in:
Benjamin Hackl 2026-11-03 21:33:31 +01:00
commit 79eb374b74
1 changed files with 19 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

15
DEVELOPMENT.md
View file

@ -82,5 +82,16 @@ As of November 2026, `gpt-5-nano` and `gpt-4.1-nano` return HTTP 500
3. Tag and push: `git tag vX.Y.Z && git push origin main vX.Y.Z`.
4. Update the version in the README's "Pinning a version" example.
CI is defined in `.gitea/workflows/ci.yml` and runs once Gitea Actions are
enabled for the repository.
## CI
CI is defined in `.github/workflows/ci.yml`, which Gitea Actions reads as
well. It runs once Actions are enabled for the repository and a runner is
available.
The workflow checks out code with `ischanx/checkout`, not
`actions/checkout`. Upstream builds the clone URL from the server's origin
and drops the `/git` subpath of imsc.uni-graz.at, so cloning fails
([actions/checkout#1370](https://github.com/actions/checkout/issues/1370)).
The fork's v6.0.2 tag fixes that; its v4 tags are identical to upstream and
do not. The action is pinned to a commit hash because it runs with the CI
token. When upgrading, review the fork's diff against upstream first.