Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

feat(action): attestation/create - Create attestation with PR map update

Open
#36 0 comments 0 reactions 1 assignee View on GitHub

@aRustyDev is already working on this.

Since Jan 27, 2026.

Assessment

This issue has not been assessed yet.

Description

enhancement new-action

Parent Epic

Part of #22 (Atomic Release Pipeline Actions)

Priority

P0 - Core attestation functionality needed by all workflows

Description

Create a composite action that wraps actions/attest-build-provenance with a consistent interface matching our other attestation actions.

This provides a unified API for generating attestations and automatically updates the PR attestation map.

Inputs

Input Required Default Description
subject-name Yes - Name for the attestation subject
subject-digest Yes - SHA256 digest of the subject
pr-number No - PR number to update attestation map
check-name No - Check name for attestation map entry
push-to-registry No false Push attestation to GHCR
token No github.token GitHub token

Outputs

Output Description
attestation-id The generated attestation ID
bundle-path Path to the attestation bundle

Usage Example

- uses: arustydev/gha/actions/attestation/create@v1
  id: attest
  with:
    subject-name: "my-chart-v1.2.3"
    subject-digest: ${{ steps.digest.outputs.digest }}
    pr-number: ${{ github.event.pull_request.number }}
    check-name: "lint-test"

Implementation Notes

  • Wraps actions/attest-build-provenance@v2
  • Optionally calls attestation/update-pr-map if pr-number provided
  • Provides consistent interface with other attestation actions

Source Reference

Used throughout helm-charts workflows:

  • validate-contribution-pr.yaml
  • validate-atomic-chart-pr.yaml
  • release-atomic-chart.yaml
Dominant language
Shell
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

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 aRustyDev/gh

All issues in aRustyDev/gh

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.