Sign releases

Open
#312 3 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
32/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
github-actions, go
Domain
release, security

Research direction

Read the release workflow and packaging or publishing configuration to determine how releases are currently produced; the issue names no files or tests. Compare that process with the suggested GitHub Actions, GitHub OIDC, and Sigstore keyless signing approach. Done means published releases can be verified as signed; check the project’s release documentation or workflow for the expected verification steps.

Written by the indexing model from the issue text.

Description

enhancement

You can even do it fully-automated via Github Actions, Github OIDC and Sigstore "keyless" signing.

Dominant language
Go
Stars
817
Forks
182
Avg merge
4h 18m
Merged PRs (30d)
6

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No 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 netsampler/goflow2

All issues in netsampler/goflow2

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.