vscode label is not automatically set yet

vscode label is not automatically set yet

should it?

On September 21, 2022, GitHub ***@***.***> wrote: vscode label is not automatically set yet

— Reply to this email directly, view it on GitHub <#614>, or unsubscribe <https://github.com/notifications/unsubscribe- auth/AAASXLGWS4L53YR26RIXXNTV7N5VVANCNFSM6AAAAAAQSO7NMA>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

should it?

I think it should.
Vim, emacs have it.
There is a lot of vscode-extensions packages.
Why not?

Any changes in vscode folder (pkgs/applications/editors/vscode/) could trigger it.

There is a label already, OfBorg just doesn't set it automatically yet:

https://github.com/NixOS/nixpkgs/pulls?q=is%3Aopen+is%3Apr+label%3A%226.topic%3A+vscode%22

Vim, emacs ..

These labels are managed in the nixpkgs repo: https://github.com/NixOS/nixpkgs/blob/master/.github/labeler.yml

ofborg only does the rebuild count and a couple of others:

ofborg/ofborg/src/tasks/eval/nixpkgs.rs

Lines 30 to 34 in c81e72c

    
           const TITLE_LABELS: [(&str, &str); 3] = [ 
        
               ("bsd", "6.topic: bsd"), 
        
               ("darwin", "6.topic: darwin"), 
        
               ("macos", "6.topic: darwin"), 
        
           ];

Oh. I did not know that. Thanks for clarifying.

	const TITLE_LABELS: [(&str, &str); 3] = [
	("bsd", "6.topic: bsd"),
	("darwin", "6.topic: darwin"),
	("macos", "6.topic: darwin"),
	];