[00:54:05] <bd808>	 I amended a MR today for the first time. It was actually a fairly smooth process once I read https://gitlab.wikimedia.org/help/user/project/merge_requests/allow_collaboration.md
[09:17:46] <wikibugs>	 10GitLab (Pipeline Services Migration🐤), 10collaboration-services: move commons-query.wikimedia.org and query.wikidata.org to kubernetes - https://phabricator.wikimedia.org/T350793 (10Gehel) Query Builder and Query GUI are owned and managed by WMDE. And change to the build process must at least be communicated...
[09:58:08] <jelto>	 GitLab needs a short restart at around 11:00 UTC
[10:03:15] <wikibugs>	 10GitLab, 10Release-Engineering-Team: `npm ci` not working on trusted runners for https://gitlab.wikimedia.org/repos/data-engineering/superset - https://phabricator.wikimedia.org/T353197 (10BTullis) @dancy - thanks so much for looking into it. I didn't spot that this ticket had been created, otherwise I would...
[10:11:22] <wikibugs>	 10GitLab (Pipeline Services Migration🐤), 10WMDE-Analytics-Engineering, 10collaboration-services: move commons-query.wikimedia.org and query.wikidata.org to kubernetes - https://phabricator.wikimedia.org/T350793 (10Jelto)
[10:27:31] <wikibugs>	 10GitLab (Account Approval), 10Release-Engineering-Team: Requesting GitLab account activation for USER[S] - https://phabricator.wikimedia.org/T353431 (10Hunsvotti)
[11:13:26] <jelto>	 GitLab restart done
[11:41:12] <wikibugs>	 10GitLab (Account Approval), 10Release-Engineering-Team: Requesting GitLab account activation for hunsvotti - https://phabricator.wikimedia.org/T353431 (10Anoop)
[14:44:53] <wikibugs>	 10GitLab (CI & Job Runners), 10Release-Engineering-Team (Onboarding 🚀): Automatically clean up unused buildkitd PersistentVolumeClaims periodically - https://phabricator.wikimedia.org/T351478 (10Sandeeps) 05Open→03In progress a:03Sandeeps
[15:47:12] <wikibugs>	 10GitLab, 10Release-Engineering-Team: `npm ci` not working on trusted runners for https://gitlab.wikimedia.org/repos/data-engineering/superset - https://phabricator.wikimedia.org/T353197 (10dancy) Thanks for the info @BTullis.  Let's leave this ticket open for a bit longer in case anyone else sees it and has s...
[15:49:00] <dancy>	 bd808: Glad to hear it! That was a bit I was a bit worried about.
[15:49:33] <wikibugs>	 10Gitlab-Application-Security-Pipeline, 10Security Team AppSec, 10Security-Team, 10Patch-For-Review, and 2 others: Address issues within certain Gitlab CI security templates - https://phabricator.wikimedia.org/T338034 (10mmartorana)
[15:51:30] <wikibugs>	 10Gitlab-Application-Security-Pipeline, 10Security-Team, 10Documentation, 10SecTeam-Processed, 10Security: Update on-wiki documentation for the AppSec Pipeline for phase 2 work - https://phabricator.wikimedia.org/T346802 (10mmartorana)
[17:02:56] <bd808>	 dancy: I think it could use some helper scripts so my fingers and eyes don't need to go into the web UI to get the fetch and push invocations, but that should be solveable. https://gitlab.wikimedia.org/help/user/project/merge_requests/reviews/index.md#checkout-merge-requests-locally-through-the-head-ref has some related tips already.
[17:04:25] <dancy>	 nod.
[17:04:39] <dancy>	 I expect gerritlab to be extended to support such operations too.
[17:05:00] <dancy>	 ala  `git review -x <gerrit-change-number>` to quickly cherry-pick a change into your repo
[17:13:39] <bd808>	 https://github.com/php/pecl-file_formats-yaml/blob/php7/dev-tools/pull-request.sh is a semi-related thing I used to use when pecl was using a strange split horizon git setup where PRs arrived on GitHub, but merges needed to land on git.php.net.
[17:25:01] <wikibugs>	 10Gitlab-Application-Security-Pipeline, 10Security-Team, 10SecTeam-Processed, 10Security, 10user-sbassett: [EPIC] Application Security Pipeline Components for Gitlab - Phase 2 Work - https://phabricator.wikimedia.org/T342177 (10sbassett)
[17:25:23] <wikibugs>	 10Gitlab-Application-Security-Pipeline, 10Security Team AppSec, 10Security-Team, 10Patch-For-Review, and 2 others: Address issues within certain Gitlab CI security templates - https://phabricator.wikimedia.org/T338034 (10sbassett)
[17:26:11] <wikibugs>	 10Gitlab-Application-Security-Pipeline, 10Security Team AppSec, 10Security-Team, 10Patch-For-Review, and 2 others: Address issues within certain Gitlab CI security templates - https://phabricator.wikimedia.org/T338034 (10sbassett) 05In progress→03Resolved
[18:42:50] <wikibugs>	 10Gitlab-Application-Security-Pipeline, 10Patch-For-Review, 10SecTeam-Processed, 10Security, 10user-sbassett: Improve related gitlab test repository - https://phabricator.wikimedia.org/T348788 (10CodeReviewBot) sbassett opened https://gitlab.wikimedia.org/repos/security/ci-cd-testing-gitlab-ci-security-t...
[21:17:38] <bd808>	 sigh. gitlab is apparently as sloppy as MediaWiki when it comes to keeping parity between the UI and the API. I just want to search for the state=blocked_pending_approval quickly -- https://gitlab.com/gitlab-org/gitlab/-/issues/276195 
[21:18:13] * bd808 will apply client side filtering with angry comments in the source code
[22:20:39] <dancy>	 A candidate for https://phabricator.wikimedia.org/project/view/6429/ perhaps?
[22:22:56] <bd808>	 If we track every missing GitLab CE feature I fear we will crash Phabricator ;)
[22:24:17] <bd808>	 The filtering on their /users api is really unintuitive, but via trial and error I got something that seems to work without iterating over every record.