grain.social/grain-ios
1 collaborator
- 1 collaborator
0
1
Pulls and issues follow templates, after knotless's
.knotless/issue.mdnew+23−0
| @@ -0,0 +1,23 @@ | ||
<!-- Title: the symptom, not the cure, at most 72 characters: "Feed | ||
jumps to the top after posting a comment". For a request, what you | ||
cannot do: "No way to reorder photos in a gallery", and keep only | ||
"What happened", as what you were trying to do and what stopped | ||
you. --> | ||
| ||
## What happened | ||
| ||
<!-- The screen and what you did, and exactly what it said: paste | ||
errors as text, not a paraphrase. A screenshot or recording helps. --> | ||
| ||
## How to see it | ||
| ||
<!-- Steps someone else can follow, from a fresh login if they can, and | ||
the gallery, profile or post involved. This matters most and is the | ||
hardest part to give: say which steps you are unsure of. --> | ||
| ||
## What you expected | ||
| ||
## Where | ||
| ||
<!-- The build number (Settings, or TestFlight), from the App Store or | ||
TestFlight; the device and iOS version. --> | ||
.knotless/pull.mdnew+33−0
| @@ -0,0 +1,33 @@ | ||
<!-- Title: what the app does once this lands, as main's log reads: | ||
"Comments keep their place when the keyboard opens". At most 72 | ||
characters, no period, never only the activity ("Fix bug", | ||
"Update feed view"). The squash commit takes this title and body | ||
as its message, so say everything here: a link is no substitute | ||
for the reason. Delete a section that has nothing to say, but keep | ||
at least one: a body with none of these headings is refused. --> | ||
| ||
## What changes | ||
| ||
<!-- What someone using Grain, or reading the code, finds different. | ||
One bold-led paragraph per part when there are several. --> | ||
| ||
## Why | ||
| ||
<!-- The problem, and why this way over the others considered. | ||
"Fixes <issue's page or at:// URI>" closes it as this merges; say | ||
what it was all the same. --> | ||
| ||
## How it was checked | ||
| ||
<!-- Tests added or run; the simulator or device and iOS version it was | ||
tried on, against which server. What is left to CI. Screenshots of | ||
what it changes on screen, attached. --> | ||
| ||
## Shortcomings | ||
| ||
<!-- What it does not do, what was not run, what could go wrong. --> | ||
| ||
## Review | ||
| ||
<!-- Optional: the kind of review wanted (a quick look, the design, | ||
one risky part) and where to start reading. --> | ||