Files
ci/checkout
ozanandZCode ac989e2c4d fix(checkout): support SHA refs — git clone --branch rejects them
A SHA in `ref` died with "Remote branch <sha> not found" (killed the
2026-11-06 sim publish of SHA f0e206ff3: dispatch ref=branch +
inputs.ref=<sha> is the publish-day pattern, since the Gitea dispatch
API only accepts branch names). SHA-shaped refs now init+fetch the sha
explicitly (the server allows anySHA fetch); branch/tag refs keep the
exact old path. Sparse path already fetched this way.

Co-Authored-By: Ozan Bozkurt <ozan@tinqs.com>
Co-Authored-By: ZCode <GLM-5.3 via ZCode>
2026-11-06 19:41:30 +00:00
..

tinqs/ci/checkout

Clones a repository from tinqs.com (self-hosted Gitea) using plain git clone.

Works on any runner with git installed — Alpine, Debian, or pre-baked images. No Node.js runtime, no GitHub API dependency.

Usage

- uses: tinqs/ci/checkout@v1

With options

- uses: tinqs/ci/checkout@v1
  with:
    repository: 'tinqs/engine'    # default: current repo
    ref: 'tinqs/main'             # default: current branch
    depth: '0'                    # default: 1 (shallow)
    token: ${{ secrets.TOKEN }}   # default: none (public clone)
    path: 'engine'                # default: . (current dir)

Inputs

Input Default Description
repository ${{ github.repository }} Repository in owner/repo format
ref ${{ github.ref_name }} Branch or tag
depth 1 Clone depth (0 = full history)
path . Directory to clone into
token `` Gitea access token for private repos