Tabla de versiones
- Dominant language
- HTML
- Stars
- 2
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
He visto vuestra tabla de versiones. Os propongo:
1. No repetir el número de versión (si es lo mismo no sé la diferencia enter elaborado y revisado, eso debería quedar en el "kanban")
1. Os sobran filas ➡️ eliminar las sobrantes
1. Usar un enlace al commit que corresponda. Es lo bueno de GitHub, puedes enlazar a otros documentos para que el que quiera vea más información. Ver [ejemplo](https://github.com/DptoSIC/proyectoEIE/commit/a934dffd1a77b013427293439357542b7f882303#diff-e485492b82c15d1f47dc7a920a80de8c).
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by finding the version table referenced in the issue and compare its rows with the project's current version history. Done means redundant rows are removed, repeated version numbers are clarified or consolidated, and each remaining entry links to its corresponding GitHub commit; workflow distinctions belong in the kanban.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100