Clarification: this was not me asking code search to actively go out and hunt for new repositories, but rather asking if it would not be a reasonable thing for those who make new repositories to adjust their processes (don't know where they are and who owns them) to always request addition here from the get go.
A lack of visibility in code search comes at a certain risk because often times its results are used to inform decisions (code reuse across projects, ...).
Comparable topic for termbox: T221835: Add CC0 License overlay popup on termbox editing. userPreferenceRepository (see) is a good place to start looking at the implementation there.
checkbox is unchecked by default
Persistence of the license notification decision was split out into T246167: Step 1: provide checkbox to not be bothered with license notification again (impact: medium).
Process question: Is it by design that newly created repositories have to have their addition to code search requested independently? Or should this request be part of another process?
C.f. T240224: Create Github and Diffusion mirrors for wikibase/vuejs-components Gerrit repository
Tue, Feb 25
Trying https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Wikibase/+/573266 I encountered the funny behavior of an empty References section during saving.
Turns out there are some getters (e.g.) guard with the help of application Status but don't take into account that one of the options is now saving.
Mon, Feb 24
Fri, Feb 21
The API will be added to the repo, not the client
Thu, Feb 20
I share this view and - conveniently - the way the task break down of T238662#5864963 went, this should be relatively straightforward thereafter.
Wed, Feb 19
Tue, Feb 18
Mon, Feb 17
Wait, why do we install vue cli in the dockerfile
I'm sorry for having put this in "Task overflow" (apparently) - that was not my intention.
Meant "tech things".
This article, in fact using jest-image-snapshot, caught my eye earlier: https://markus.oberlehner.net/blog/visual-regression-tests-for-vue-applications-with-jest-and-puppeteer/
Also offers background and instructions for the puppeteer setup and a sample repo.
Fri, Feb 14
https://gerrit.wikimedia.org/r/571482 is an attempt at reducing the size, but without changing the content. "Tree shaking" (e.g. https://github.com/indutny/webpack-common-shake/) is a much harder problem, and - if it were added - would have to come as an earlier step (i.e. before uglify).
Thu, Feb 13
Wed, Feb 12
Tue, Jan 28
Jan 27 2020
Intermediate state (how a repo item permission error currently looks like on my system) integrated into MW: