Commit faf448aef4
Verified · cmc
Layout: unified · split
Parity.org +10
| @@ -40,6 +40,7 @@ browser-only and the iOS build screen unable to say more than the log. | ||
| 40 | 40 | | create | yes | yes | yes | |
| 41 | 41 | | create from a fork | yes | no | yes | |
| 42 | 42 | | milestone | yes | yes | yes | |
| 43 | | choose body markup | yes | no | no | | |
| 43 | 44 | |
| 44 | 45 | Diff-line comments are the one place the web trails: krz/gitbay#44. |
| 45 | 46 | Creating from a fork works anywhere the source can be typed as |
| @@ -57,6 +58,15 @@ Creating from a fork works anywhere the source can be typed as | ||
| 57 | 58 | | labels, assignees | yes | yes | yes | |
| 58 | 59 | | milestone | yes | yes | yes | |
| 59 | 60 | | milestone list | yes | yes | yes | |
| 61 | | choose body markup | yes | no | no | | |
| 62 | ||
| 63 | Issue, MR and release bodies, and their comments, carry the markup they | |
| 64 | were written in — =--format md|org= on create, comment and edit, stored | |
| 65 | alongside the text so changing a preference later cannot reinterpret | |
| 66 | prose that already exists. Every surface *renders* the stored format; | |
| 67 | the =no= above is the absence of a picker on the web form and in the iOS | |
| 68 | composer, both of which write markdown. Diff-line comments have no | |
| 69 | format column and are always markdown. | |
| 60 | 70 | |
| 61 | 71 | * Repositories |
| 62 | 72 | |