Sign in

Search issue titles and bodies, change requests and comments. Private repositories you cannot read are not included.

vole
Clone

Read only, no credentials:

https://rodent.software/git/vole.git

Write over SSH with a registered key:

git clone ssh://git@0.0.0.0:2222/vole.git

A free and open-source forge that lives in your Git repo.

Edit issue and change details in place

802e0e52533746522b3e65b953e5cc0141aa70b9 · Keenan Nemetz · 4d ago · parent 90f1ab59

Edit issue and change details in place

Put the title pencil beside the heading and the description menu on its card, matching the comment editor. Each control saves only its own field: the title response is the heading and the description response is the card, so an open draft in the other field is not replaced. The standalone /edit page stays as the fallback.

Prefilled edit fields size themselves to their content and remain vertically resizable. Prose copied from a menu is query-escaped in the attribute, so untrusted markdown in an issue or comment cannot appear verbatim in the page.

docs/issues.md +5−3

@@ -99,9 +99,11 @@ same metadata writer the CLI uses, so it is the same file on the same branch. A
99 99 contributor can use this form or the CLI; pre-receive asks the same capabilities the
100 100 form does, so neither offers more than the other.
101 101
102 The issue's author or a maintainer can correct its title and description with
103 **Edit** on the issue page. The discussion, labels, and assignees are left alone,
104 and the edit is an ordinary metadata commit like the one the CLI writes.
102 The issue's author or a maintainer can correct its title with the pencil beside
103 the heading, or its description from the card's menu. Each opens its own field in
104 place, so saving does not leave the page or replace the discussion. The discussion,
105 labels, and assignees are left alone, and the edit is an ordinary metadata commit
106 like the one the CLI writes.
105 107
106 108 ## Using the CLI
107 109