Description
Details
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Add wikibase-vuejs-components and wikibase-termbox | labs/codesearch | master | +2 -1 |
Related Objects
Event Timeline
Change 574873 had a related patch set uploaded (by Ladsgroup; owner: Ladsgroup):
[labs/codesearch@master] Add wikibase-vuejs-components and wikibase-termbox
Change 574873 merged by jenkins-bot:
[labs/codesearch@master] Add wikibase-vuejs-components and wikibase-termbox
Mentioned in SAL (#wikimedia-cloud) [2020-02-25T21:50:50Z] <Amir1> sudo service hound-libraries restart (T246120 T246121)
Awesome, thanks.
https://codesearch.wmflabs.org/search/?q=wikibase-vuejs-components&i=nope&files=&repos=wikibase-vuejs-components
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
I co-maintain this at my volunteer capacity, it doesn't belong to any engineering teams so I think it should be made separately. I personally (can't talk on behalf of other maintainers) wouldn't add them unless there's the need. Like someone needs this repo in codesearch.
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 if/where they are documented 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, ...).