Epic: real before/after cases on the owner's own repositories

Abierto
  • ¿Algo no está bien?
#88 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
github, python
Área
documentation

Línea de trabajo

Read sub-issue #80 for the repeatable workflow, then review #81–#83 and the candidate table in this issue. Start with the workflow and candidate selection; done means at least one honest before/after case is published in BeautifulRepo with immutable SHAs, observed output, and stated limits, meeting the related acceptance in #32.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

epic real-case

Goal

Prove that the handbook works on real repositories. Take one of the owner's public repositories, improve it with BeautifulRepo's tools and guides through a normal PR in that repository, then publish an honest before/after case inside BeautifulRepo with immutable SHAs, observed output and stated limits.

Candidate review (13 public repositories, BeautifulRepo d55594d, 2026-10-22)

Repository Type Licence Suitability Reason
PatchPitch local-AI app MIT 5 Large visible change; an offline demo already exists
trade_simulation simulation + viewer MIT 4 README claims lag behind released M4 / v0.4.0
Quillgrain + Common CLI + data pack MIT 4 Small, offline after install; two project types
Dayflare data app none 3 Best offline first run, but ideas-only until licensed
Playmancer browser app none 3 Ideas-only until licensed
Devostasis CLI MIT 3 Change too small; already in case-studies/first-patterns.md
CompostClub local-AI web app MIT 2 Follows BeautifulRepo from its first commit, so there is no honest "before"; use it as a positive reference
HungryCrab CLI + plugin MIT 2 Already mature
Scriptorium CLI + site none 2 Unlicensed and large
EndlessZenFramework prompt kit MIT 2 First success isn't reproducible offline
DrevenGames static page none 2 Tiny
landings empty – 1 Empty

Sub-issues

  1. #80: the repeatable workflow (snapshot → audit → PR in target → snapshot → write-up). Do this first.
  2. #81: PatchPitch.
  3. #82: trade_simulation.
  4. #83: Quillgrain and Quillgrain_Common.
  5. #32: the first completed case satisfies its acceptance.

Quick fixes found along the way (in other repositories, not tracked here)

  • DrevenGames README:12 privacy-policy URL returns 404; the /DrevenGames/ path works.
  • HungryCrab and Quillgrain SECURITY.md point to private vulnerability reporting, which is disabled on both.
  • Devostasis README:233 writes a link as a bare github.com/... path, so it resolves as a missing relative file.

Related: #32

Lenguaje dominante
Python
Estrellas
2
Forks
0
Merge medio
4 h 32 min
PR fusionados (30 d)
148

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 drevendev/BeautifulRepo

Todos los issues de drevendev/BeautifulRepo

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.