Epic: "Meta Data Table" in Issue Description
Nobody has claimed this yet.
Assessment
This issue has not been assessed yet.
Description
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)
- a comment advising people not to delete/change it.
-
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:
-
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
- Dominant language
- Elixir
- Stars
- 33
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dwyl/github-backup
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 15/100
dwyl/github-backup#138 ·
-
discuss enhancement priority-2
dwyl/github-backup#136 · 10 comments · 1 assignee ·
-
😕 Openhelp wanted priority-2
Difficulty 5/5 Over a week Newbie friendliness 25/100
dwyl/github-backup#135 · 1 comment · 3 reactions ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 20/100
dwyl/github-backup#133 ·
-
discuss priority-4 technical
Difficulty 5/5 Over a week Newbie friendliness 20/100
dwyl/github-backup#132 · 3 comments · 1 reaction ·
All issues in dwyl/github-backup
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
agentjido/jido_harness#80 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
sevenseacat/cinder#235 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
phoenixframework/phoenix#6847 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 64/100