Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Document commit signing: rationale, setup, and org-wide enforcement

Abierto
  • ¿Algo no está bien?
#12 0 comentarios 0 reacciones 1 asignado Ver en GitHub

@Ethan-Arrowood ya está trabajando en esto.

Desde el 10/7/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

Summary

Write a commit signing guideline doc. We want to enforce commit signing across the org — all commits to all HarperFast repos, with public-facing OSS repos as the highest priority, should be signed.

Doc outline

The doc should be structured in this order:

1. Why commit signing matters

Open with the rationale: signed commits cryptographically verify that a commit actually came from the person it claims to be from. Cover the threat model briefly — author spoofing (anyone can set user.name/user.email to anything), supply chain integrity for our OSS consumers, and the "Verified" badge as a trust signal on public repos.

2. How to set it up

Link out to setup resources rather than duplicating them:

3. How we enforce it

Link to the enforcement mechanisms and document which ones we use:

  • Org-level: rulesets at the organization level with the "Require signed commits" rule
  • Repo-level: branch protection / repo rulesets requiring signed commits on default branches
  • Document the actual settings we apply so repo admins can verify their repo is compliant
4. AI agent workflows

Platform enforcement (rulesets, CI, hooks) is the backstop, but AI agents are a major producer of commits and a major reviewer of PRs — the guideline should be embedded in agent workflows too, especially in the window before hard enforcement is rolled out:

  • Producing commits: skills / agent instructions (e.g. in the skills repo, CLAUDE.md/AGENTS.md conventions) should instruct agents that commits they author must be signed — verify the environment's signing config (git config commit.gpgsign, signing key present) before committing, and surface a warning rather than silently producing unsigned commits.
  • Reviewing PRs: PR-review skills should include a commit check step — flag unsigned/unverified commits in review output. This gives us soft enforcement via agent review before org rulesets are turned on.

The doc should note this pattern; actually updating the individual skills can be follow-up work.

5. Effective date

Short closing section: this policy was adopted in July 2026. Enforcement applies to commits from this point onward — historical unsigned commits are grandfathered in and do not need to be rewritten. Only new commits are required to pass signature verification.

Acceptance criteria

  • Doc added to this repo following the sections above
  • Enforcement settings (org ruleset and/or repo-level guidance) documented
  • AI agent workflow guidance included (agents sign their commits; review skills check for signatures)
  • Effective date (July 2026, forward-looking only) stated
Lenguaje dominante
JavaScript
Estrellas
3
Forks
0
Sin PR fusionados en 30 d

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de HarperFast/code-guidelines

Todos los issues de HarperFast/code-guidelines

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.