chore(repo): documentación técnica, cumplimiento legal y reglas de formato (pre-main) - #77
Merged
Merged
Conversation
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
chore/repo-housekeeping-pre-main
Descripción
En este ciclo de preparación previo a la integración hacia nuestra rama de producción, estructuramos la documentación fundamental del repositorio, garantizamos el cumplimiento de las políticas de almacenamiento local y establecemos barreras de estandarización para el código fuente.
Detalles técnicos que integramos:
docs): Integramos elREADME.mden la raíz del proyecto, centralizando la documentación completa de la plataforma (arquitectura, requerimientos y flujos de ejecución).feat): Desarrollamos la vista de políticas legales (cookies.html) y conectamos los puntos de acceso desde la interfaz principal (index.html), proveyendo transparencia sobre el almacenamiento de sesión.chore): Implementamos el archivo.editorconfigpara forzar reglas estrictas de formato (espacios, saltos de línea, codificación) previniendo divergencias de estilo o ruido en los futuros diffs independientemente del editor de código utilizado.Tipo de cambio
Cómo probar
README.mdy.editorconfigfueron detectados y procesados correctamente por el IDE (ej. VS Code).cookies.html).Checklist
.editorconfig