[05:40:25] andrewbogott: I indicated https://wikitech.wikimedia.org/wiki/News/Cloud_VPS_2022_Purge#packagist-mirror can be deleted [07:50:02] !log packagist-mirror deleted project per https://wikitech.wikimedia.org/wiki/News/Cloud_VPS_2022_Purge#packagist-mirror [07:50:04] taavi: Unknown project "packagist-mirror" [07:50:12] !log admin deleted project packagist-mirror per https://wikitech.wikimedia.org/wiki/News/Cloud_VPS_2022_Purge#packagist-mirror [07:50:14] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Admin/SAL [08:25:22] heh, ty :D [20:51:45] (not urgent at all) do we have any good ways to push to repo from toolforge these days? [21:20:11] chicocvenancio: haven't used it myself, but I'd probably set up something like https://gitlab.wikimedia.org/help/user/project/settings/project_access_tokens [21:21:02] github lets you create a deploy SSH key for the same effect, https://docs.github.com/en/developers/overview/managing-deploy-keys [21:21:10] yeah, my project is in github, I used a similar thing, its still a bit icky... [21:21:56] what makes it icky? [21:22:46] toolforge roots have access to my repo now, its very easy to commit the secret world readable on disk [21:24:12] I don't think there's any way you can push via toolforge without roots having some way to intercept it [21:24:41] and yeah, I like github's ssh key over a HTTPS access token because ssh will usually yell at you if the permissions are insecure [21:25:20] I don't think I can set the keys to expire or have limited scope as I can with PATs though [21:25:54] https://docs.gitlab.com/ee/user/project/deploy_keys/ supposedly gitlab does support ssh keys [21:26:59] anyway, thanks for the response [21:27:51] gitlab group membership can expire, so I suppose you could create a real user w/ ssh key, and then have their membership in the relevant group be as restricted as you want and expire as desired