Support custom buildTypes?

Open
#195 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
github-actions, typescript
Domain
ci-cd, security

Research direction

Start with the referenced hook.sh and .github/workflows/ci.yml, then trace the attestation upload path and the validation that rejects https://nixos.org/build/v1. Compare that behavior with the documented supported build types and custom predicate types. Done means the requested custom buildType behavior is defined, implemented or documented, and verified through the referenced workflow.

Written by the indexing model from the issue text.

Description

I'm trying to upload a SLSA predicate with a custom buildType

https://github.com/arianvp/nix-attest/blob/86781ad55047cefbe3ae8ea8fd2fab838aedc36b/hook.sh#L59
https://github.com/arianvp/nix-attest/blob/86781ad55047cefbe3ae8ea8fd2fab838aedc36b/.github/workflows/ci.yml#L68

However during upload I get an error:

https://github.com/arianvp/nix-attest/actions/runs/12681357992/job/35344912224

Error: Error: Failed to persist attestation: Invalid Argument - unsupported build type: https://nixos.org/build/v1 - https://docs.github.com/rest/repos/repos#create-an-attestation

however nowhere is documented what build types are supported. Furthermore It would be great if custom build types are allowed just like custom predicate types

Dominant language
TypeScript
Stars
187
Forks
65
Avg merge
3d 8h
Merged PRs (30d)
8

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from actions/attest

All issues in actions/attest

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.