Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Epic: "Meta Data Table" in Issue Description

Abierto
#14 8 comentarios 2 reacciones 2 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

enhancement epic please-test priority-2 question

As a user of the GitHub Backup App,
I want to see at a glance if an issue has "version history"
so that I know there is "history" and I can click to see it!

Acceptance Criteria

  • Meta Table should be inserted into the issue description when the issue is Created.

    • a comment advising people not to delete/change it.
      e.g: <!-- avoid editing below this line to preserve issue history --> (see below)

  • Minimise space occupied by the table to Two Rows to avoid clutter:
    Heading (Key) & Row-Cell (Value) >> see below for example.

  • Display the revision count for the issue.
    We already have a "Proof of Concept" for using SVG as a Counter: http://hits.dwyl.io
    e.g: HitCount

  • Display a "short link" (dependent on the App / Domain Name chosen. see: #13)

Optional (Nice-to-Have)

  • Subtle Color/Branding in the table.

Question / Discussion:

What other info would it be useful to display in the "Meta Table"?
(or should we "keep it simple for MVP and ask users once deployed...?)

Example:

Issue Edit Count View History
9 gibu.io/dwhq321

Note: I would prefer to have a single-line table (for even less "clutter") e.g:

+---------------------+-------------------------------+
| Issue Edit Count: 9 | View History: gibu.io/dwhq321 |
+---------------------+-------------------------------+

But sadly markdown does not support it:
https://stackoverflow.com/questions/17536216/create-table-without-header-in-markdown

Lenguaje dominante
Elixir
Estrellas
33
Forks
3
Sin PR fusionados en 30 d

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

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 dwyl/github-backup

Todos los issues de dwyl/github-backup

Issues similares

Más issues de Elixir

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.