grain.social/grain
photography-focused photo sharing platform
grain.social
1 collaborator
- 1 collaborator
0
2
Pulls and issues follow templates, after knotless's
.knotless/issue.mdnew+24−0
| @@ -0,0 +1,24 @@ | ||
<!-- Title: the symptom, not the cure, at most 72 characters: "Gallery | ||
page shows no photos after an edit". 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 page or call, and exactly what it said: paste errors and | ||
output as text, not a paraphrase. --> | ||
| ||
## How to see it | ||
| ||
<!-- Steps someone else can follow, from a fresh login if they can, and | ||
the gallery, profile or record's URL or at:// URI. This matters most | ||
and is the hardest part to give: say which steps you are unsure | ||
of. --> | ||
| ||
## What you expected | ||
| ||
## Where | ||
| ||
<!-- grain.social or a local dev server; the web, iOS or Android; the | ||
browser or device; the commit you ran, if not what is deployed. --> | ||
.knotless/pull.mdnew+34−0
| @@ -0,0 +1,34 @@ | ||
<!-- Title: what grain does once this lands, as main's log reads: | ||
"Private galleries open on zds as they do on pds.js". At most 72 | ||
characters, an optional area prefix ("web: …", "server: …"), no | ||
period, never only the activity ("Fix bug", "Update feeds"). | ||
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, what was tried in the browser or the apps | ||
against which server. What is left to CI. Screenshots of what it | ||
changes on a page, 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. --> | ||