Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

feat(framework): make implementation commits obey project policy

Aperta
#413 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
55/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
git, typescript
Ambito
developer-experience, tooling

Direzione di ricerca

Trace the VCS-memory template and implementation flow to find where commit policy is generated, resolved, and applied. Inspect the existing verification, branch, commit, and hook-handling paths first; done means absent or never prevents commits, enabled policies create atomic verified commits only on non-default branches, and hook rejection stops clearly without pushing or including unrelated changes.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Need

An AI implementing an approved plan may create small, reviewable local commits while it works. This behavior must be governed by the project policy, not hard-coded by the implementation flow.

Current gap

The VCS-memory template exposes commit-cycle choices, while the implementation flow always commits each verified phase. As a result, the documented never choice is not enforceable and the policy does not state the safety boundary.

Scope

  • Project memory records one explicit automatic-commit policy, including when commits may occur and when they may not.
  • The implementation flow resolves and obeys that policy. If it is absent or set to never, it makes no automatic commit.
  • When enabled, an automatic commit contains one verified unit of work and follows the project VCS convention.
  • Automatic commits run only on a non-default working branch. They never push, force-push, amend history, or include unrelated pre-existing changes.
  • A rejected hook stops the flow and reports the reason; it does not retry blindly.

Out of scope

  • Creating a new skill, hook, or background agent.
  • Automatic pull requests, remote pushes, rebases, or branch deletion.

Acceptance criteria

  • Generated VCS memory expresses the project policy in actionable terms, including the branch and push boundaries.
  • never and an absent policy produce no automatic commit during implementation.
  • An enabled policy produces only atomic commits after the configured verification point.
  • The implementation flow cannot automatically commit on the default branch or push a commit.
  • A hook rejection leaves no new commit and gives a clear stop reason.
Lingua principale
TypeScript
Stelle
481
Fork
45
Merge medio
14h 27m
PR unite (30g)
111

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di ai-driven-dev/framework

Tutte le issue di ai-driven-dev/framework

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.