SCM SourceHut

SourceHut

SourceHut has no commit-status API; instead the relay reports build results by submitting a tiny job manifest to builds.sr.ht whose single step echoes the original run's state and exits 0 (success) or non-zero (failure) — making the Tekton result visible (and linkable) in the SourceHut build list for that commit.

Actions: commit_status (via builds.sr.ht job submission).

Authentication

scm:
  sourcehut:
    - name: sourcehut
      enabled: true
      base_url: https://builds.sr.ht
      auth:
        secretRef:
          name: srht-token                 # Secret key: token (OAuth2 personal token)

Required annotations

scm.provider = instance name; scm.repo-owner (the ~user) + scm.repo-name; scm.commit-sha.

How it looks

The submitted manifest references https://git.sr.ht/~<owner>/<repo>#<sha> as its source and is tagged tekton + your scm.context, so builds are filterable. Job note = the event description.

Comment templates

SourceHut exposes only commit_status (no comment actions), so there is no comment template / configmapRef to configure here. Template supply for providers that do support comments is documented in Actions → Comment templates are optional.