chore: implement professional github issue forms and pr templates#13
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🎯 Propósito de este PR
Este Pull Request estandariza y profesionaliza el flujo de contribución del repositorio de BUMI. Se migra de plantillas de texto libre a GitHub Issue Forms (YAML), garantizando que todos los reportes de errores y solicitudes de nuevas funcionalidades ingresen con la estructura, contexto y metadatos necesarios desde el primer momento.
🛠️ Cambios Realizados
1. Formularios de Issues (
.github/ISSUE_TEMPLATE/)Se implementaron 4 formularios interactivos con validación de campos obligatorios, menús desplegables y asignación automática de etiquetas:
bug_report.yml: Estructura estricta para pasos de reproducción, entorno de ejecución (dropdown) y advertencias de seguridad para evitar fuga de credenciales. Etiquetas automáticas:bug,triage.feature_request.yml: Enfoque en la resolución de problemas, con sección obligatoria para la Definición de Hecho (DoD). Etiqueta automática:enhancement.documentation.yml: Canal específico para reportar mejoras o errores en la documentación. Etiqueta:documentation.general_report.yml: Para consultas no estandarizadas. Etiqueta:question.2. Gobernanza del Repositorio
config.yml: Se deshabilitaron los blank issues (blank_issues_enabled: false) para forzar a los contribuyentes a usar las plantillas oficiales, reduciendo el ruido en el tracker.3. Plantilla de Integración
pull_request_template.md: Nueva estructura que exige referenciar el issue que soluciona (Closes #), definir el tipo de cambio y un checklist de verificación de calidad (lint/build).✅ Checklist de Validación (0vethor0)
npm run lintynpm run build) completada sin errores.chore/github-standardization) para este propósito.