Commit d775997ead
Verified · cmc
Layout: unified · split
.gitbay/wiki/Parity.org +8
| @@ -113,6 +113,9 @@ reviews, since an approval was of the diff against the old branch. | ||
| 113 | 113 | | choose body markup | yes | yes | yes | |
| 114 | 114 | | issue templates | yes | yes | yes | |
| 115 | 115 | | milestone create, close, reopen | yes | no | yes | |
| 116 | | org labels: set, list, remove | yes | list | no | | |
| 117 | | org milestones: create, list, close, reopen | yes | list | no | | |
| 118 | | closes across repositories | yes | yes | yes | | |
| 116 | 119 | |
| 117 | 120 | Labels are created on the fly by =issue label --add= and managed by |
| 118 | 121 | =label list=, =label set <label> --color rrggbb= and =label remove=, |
| @@ -121,6 +124,11 @@ on every chip and derives one from the name when none is set. The set | ||
| 121 | 124 | itself is at =/<owner>/<repo>/labels=, linked from the issue list: |
| 122 | 125 | create, recolour and remove, dispatching the same commands. |
| 123 | 126 | |
| 127 | Org labels and milestones are managed on the CLI and API only; | |
| 128 | =/<org>/-/labels= and =/<org>/-/milestones= show them. The repository | |
| 129 | label page's form exists for colour alone, and three org forms nobody | |
| 130 | asked for were not worth their handlers. | |
| 131 | ||
| 124 | 132 | Issue, MR and release bodies, and their comments, carry the markup they |
| 125 | 133 | were written in — =--format md|org= on create, comment and edit, stored |
| 126 | 134 | alongside the text so changing a preference later cannot reinterpret |
.gitbay/wiki/Users.org +21 −1
| @@ -347,7 +347,9 @@ pages carry the discovery link. | ||
| 347 | 347 | Commit messages act on issues when the commits land on the default |
| 348 | 348 | branch (direct push or MR merge): =closes/fixes/resolves #4= closes the |
| 349 | 349 | issue with a linking comment, and a bare =#4= leaves a reference |
| 350 | comment. Each issue/commit pair acts once, ever. Same repository only. | |
| 350 | comment. Each issue/commit pair acts once, ever. =Closes owner/name#N= closes an issue in another repository when | |
| 351 | you hold write there; otherwise it stays a plain link. A bare | |
| 352 | =owner/name#N= links and does nothing. | |
| 351 | 353 | |
| 352 | 354 | Milestones group issues and MRs toward a release (write access to |
| 353 | 355 | manage, attach with =issue milestone= / =mr milestone=; progress shows |
| @@ -359,6 +361,24 @@ gitbay milestone list [--state open|closed|all] | ||
| 359 | 361 | gitbay milestone close v1.0 / reopen v1.0 |
| 360 | 362 | #+end_src |
| 361 | 363 | |
| 364 | An org holds labels and milestones every repository under it sees | |
| 365 | beside its own. =issue label --add=, =issue milestone= and =mr | |
| 366 | milestone= resolve the org's row first; a repository cannot create a | |
| 367 | label or milestone with a name its org holds. Creating an org label or | |
| 368 | milestone whose name repositories under the org already use folds them | |
| 369 | in: their issues and merge requests move to the org's row. Org admins | |
| 370 | manage them; counts span the repositories you can read. | |
| 371 | ||
| 372 | #+begin_src sh | |
| 373 | gitbay org label set acme bug --color cf222e | |
| 374 | gitbay org label list acme / remove acme bug | |
| 375 | gitbay org milestone create acme v2 --due 2027-03-01 | |
| 376 | gitbay org milestone list acme [--state open|closed|all] | |
| 377 | gitbay org milestone close acme v2 / reopen acme v2 | |
| 378 | #+end_src | |
| 379 | ||
| 380 | On the web: =/acme/-/labels= and =/acme/-/milestones=, read-only. | |
| 381 | ||
| 362 | 382 | Issue templates: commit =.gitbay/issue-template.md= (and optional |
| 363 | 383 | =issue-template-<name>.md= variants) to the default branch. =gitbay |
| 364 | 384 | issue create= prefills =$EDITOR= with the default template, the web |