Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

Epic: "Meta Data Table" in Issue Description

未关闭
#14 8 条评论 2 个 reaction 已指派 2 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

这个 Issue 还没有评估数据。

描述

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

主要语言
Elixir
星标
33
派生
3
30 天内没有已合并 PR

贡献指南

这个仓库没有索引到贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

dwyl/github-backup 的其他 Issue

查看 dwyl/github-backup 的全部 Issue

相似的 Issue

更多 Elixir Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。