Hilton Chain <hako@ultrarare.space> writes: > Hi Guix, > > An initial set of labels were added in > https://codeberg.org/guix/guix/issues/33. > > Documentation for labels are available here: > https://forgejo.org/docs/latest/user/labels/ > > Once created, an id will be assigned > e.g. https://codeberg.org/guix/guix/issues?labels=422985 > > Labels can be deleted, all its information can be edited as well. And > labels with duplicated names are allowed. (We should not make that > happen.) > > > Our current naming convention is "prefix + name": > > 1. prefix ends with '/' for exclusive labels, e.g. ‘kind/’, and '-' for > non-exclusive ones, e.g. ‘team-’. > 2. names follows the same convention for variable names. > > Below are the initial set of labels. > > - kind/bug > #e11d21 Confirmed bug reports. > - kind/moreinfo: > #fbca04 Need more information for further action. > - kind/wishlist > #009800 Feature and package requests. > - kind/wont-fix: > #000000 Out of scope. >
> Labels for teams are added as well, descriptions from etc/teams.scm are
> used. Currently they are labelled to pull requests manually, eventually
> we should automate the process.
A file should be added to write down these labels
etc/labels.scm:
#+begin_src scheme
;; I suggest that the security fix could be a label, so that it can be
;; quickly filtered and applied
(label (name "security-fixes")
(color "red")
(description "Security fixes for the package."))
;; And I suggest learning nixpkgs, add the label of how many packages need
;; to be build.
;;; rebuild-1-100 rebuild-101-300 rebuild-301-2000 ...
(list (label (name "rebuild-1-100")
;; It might be the colors that gradually change in sequence.
(color "")
(description name))
...)
;;
;; And first-contribution
(label (name "first-contribution")
;; maybe yellow?
(color "")
(description "This is the first contribution"))
#+end_src
>
> Thanks
signature.asc
Description: PGP signature
