Tim Jacomb

Please provide more information, i.e. scopes, what resolution strategy you have configured in your global config?

the resolution strategy for slack IDs? it's in the advanced settings on the global configuration

No in your jenkins configuration, system configuration page

We use the header not the query string: https://github.com/jenkinsci/slack-plugin/blob/955756034a9addb3fbbed7b741c564a36b112a4b/src/main/java/jenkins/plugins/slack/user/EmailSlackUserIdResolver.java#L137

🤷 https://www.exygy.com/blog/which-license-should-i-use-mit-vs-apache-vs-gpl

I tried this on https://github.com/jenkinsci/bom The formatting of the file gets broken really badly after apply: ``` updatecli apply -c updatecli/updatecli.d/weekly.yaml ``` `git apply file.patch` ```diff diff --git a/sample-plugin/pom.xml b/sample-plugin/pom.xml...

I'm going the install update cli directly to agent approach instead for now

cc @janfaracik

Looking at the textbox sample I believe I was thinking of the auto complete which at least supports keyboard navigation

Should be fixed by https://github.com/jenkinsci/jenkins/pull/6408 which is blocked on https://github.com/jenkinsci/matrix-auth-plugin/pull/120